[lkml]   [2001]   [Sep]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] /dev/epoll update ...

On 21-Sep-2001 Ton Hospel wrote:
> In article <>,
> Davide Libenzi <> writes:
>> On 19-Sep-2001 Christopher K. St. John wrote:
>>> Davide Libenzi wrote:
>> Again :
>> 1) select()/poll();
>> 2) recv()/send();
>> vs :
>> 1) if (recv()/send() == FAIL)
>> 2) ioctl(EP_POLL);
> mm, I don't really get the second one. What if the scenario is:
> In the place you are in your program, you now decide that a
> read is in order. You try read, nothing there yet,
> the syscall returns, the data event happens and THEN you go into
> the ioctl ?
> Possibilities seem:
> 1) You hang, having missed the only event that will happen
> 2) Just having data triggers the ioctl (maybe only the first time),
> why not leaving out the initial read then and just do it afterwards
> like select ?
> 3) It generates a fake event the first time you notify interest, but then
> the startup case leads to doing the read uselessly twice.
> Or is there a fourth way I'm missing this really works ?

That was a simplified function :

while (recv()/send() == FAIL)

this is the right code.
If an event happens between the recv() and the ioctl() this is cached by the
driver and it'll be returned from ioctl().

- Davide

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:17    [W:0.124 / U:0.128 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site