home
> blog
>> 756
| [previous] / [up] | [overview] | [down] / [next] |
Fri Jun 15 18:01:41 2012 GMT: jabberd2 broke after upgrade to Ubuntu 12.04
Fri Jun 08 22:58:54 2012 GMT: Salome @ Royal Opera House
Mon Jun 04 16:55:23 2012 GMT: Berlin
I have just added some pictures of Berlin to my photo album: part 1 and part 2.
Sun May 20 13:59:05 2012 GMT: Falstaff @ Royal Opera House
I have been to a performance of Falstaff at the Royal Opera House yesterday evening.
Mon May 14 22:23:38 2012 GMT: La bohème @ Royal Opera House
Just been to a performance of La bohème at the Royal Opera House.
Sat May 05 16:09:16 2012 GMT: Cologne
I have added some pictures from my stop-over in Cologne to my photo album.
Sun Apr 29 16:08:27 2012 GMT: EPOLLOUT|EPOLLET Behaviour
Continuing my investigation of EPOLLOUT|EPOLLET behaviour I have now looked at different socket types (and updated the test code). This now shows that the behaviour described in the epoll man page actually only applies to TCP sockets and varies quite a bit for other socket types.
For UDP sockets you get an EPOLLOUT event when the send operation completes, whereas with UNIX domain sockets you get an EPOLLOUT event when the data has been read by the peer. And finally, with UNIX pipes you get an event when the send operation completes and another event when the data is read by the peer.
Unfortunately, this doesn't appear to be documented anywhere and you are essentialy left with testing what the behaviour is or trying to read the kernel source code. There was a somewhat related discussion on the Linux netdev mailing list a few years ago regarding the EPOLLOUT behaviour for TCP sockets.
Sun Apr 22 19:18:47 2012 GMT: Design and Analysis of Algorithms I
Sat Apr 21 19:24:24 2012 GMT: boost asio thread contention
Sat Apr 21 14:51:42 2012 GMT: Spurious EPOLLOUT events
Sun Apr 01 11:03:28 2012 GMT: Run, Christof, Run
Thu Mar 29 20:43:00 2012 GMT: boost asio 1.46.1 vs. boost asio 1.49.0
