<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (michielbuddingh)</title>
    <link>https://pinboard.in/u:michielbuddingh/public/</link>
    <description>recent bookmarks from michielbuddingh</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://www.outflux.net/blog/archives/2008/03/09/using-select-on-a-fifo/"/>
	<rdf:li rdf:resource="http://www.kernel.org/doc/man-pages/online/pages/man2/signalfd.2.html"/>
	<rdf:li rdf:resource="http://lwn.net/Articles/245533/"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://www.outflux.net/blog/archives/2008/03/09/using-select-on-a-fifo/">
    <title>codeblog » using select on a fifo</title>
    <dc:date>2009-11-05T13:35:37+00:00</dc:date>
    <link>http://www.outflux.net/blog/archives/2008/03/09/using-select-on-a-fifo/</link>
    <dc:creator>michielbuddingh</dc:creator><description><![CDATA[" ... When dealing with sockets, the above loop is sane — EOF means the other end hung up and you’ll never get more data from the file descriptor. In the case of a FIFO, however, “0 length read” means there are no more FIFO writers — but more could attach later and continue feeding in data! The problem with this is that select misbehaves and marks the file descriptor as “EOF” forever. Only the initial select() call blocks until there is something to read — once it hits EOF, select will always immediately return, defeating the purpose of select() ... "]]></description>
<dc:subject>asynchronous select poll fifo</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:michielbuddingh/b:ac3293386b6b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:asynchronous"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:select"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:poll"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:fifo"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.kernel.org/doc/man-pages/online/pages/man2/signalfd.2.html">
    <title>signalfd(2)</title>
    <dc:date>2009-10-30T09:10:11+00:00</dc:date>
    <link>http://www.kernel.org/doc/man-pages/online/pages/man2/signalfd.2.html</link>
    <dc:creator>michielbuddingh</dc:creator><description><![CDATA[" ... signalfd() creates a file descriptor that can be used to accept signals targeted at the caller. This provides an alternative to the use of a signal handler or sigwaitinfo(2), and has the advantage that the file descriptor may be monitored by select(2), poll(2), and epoll(7) .. "]]></description>
<dc:subject>linux programming signals asynchronous events</dc:subject>
<dc:identifier>https://pinboard.in/u:michielbuddingh/b:da0437393a47/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:linux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:signals"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:asynchronous"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:events"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://lwn.net/Articles/245533/">
    <title>timerfd() and system call review [LWN.net]</title>
    <dc:date>2009-10-30T09:09:14+00:00</dc:date>
    <link>http://lwn.net/Articles/245533/</link>
    <dc:creator>michielbuddingh</dc:creator><description><![CDATA[" ... Now consider the timerfd() system call, which was added to the 2.6.22 kernel. The purpose of this call is to allow an application to obtain a file descriptor to use with timer events, eliminating the need to use signals ... "]]></description>
<dc:subject>linux asynchronous events programming</dc:subject>
<dc:identifier>https://pinboard.in/u:michielbuddingh/b:0a6b25a41b23/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:linux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:asynchronous"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:events"/>
	<rdf:li rdf:resource="https://pinboard.in/u:michielbuddingh/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>