Messages in this thread |  | | Date | Fri, 21 Sep 2001 14:36:23 -0700 (PDT) | From | Davide Libenzi <> | Subject | Re: /dev/yapoll : Re: [PATCH] /dev/epoll update ... |
| |
On 21-Sep-2001 Christopher K. St. John wrote: > Davide Libenzi wrote: >> >> By reporting the initial state of the connection will >> make /dev/epoll to be a hybrid interface >> > > Yes, but you need that anyway (see below) > > >> and looks pretty crappy to me. >> > > It turns out that a hybrid interface is needed > in any case to handle overload. When the queues > start to fill up, you need to back off and start > basically doing something like a plain-old-poll() > instead. Ref the paper. Here's a link to a kernel > list dicussion that covers similiar ground:
Now, my question born spontaneously :
"Did you read and understood the /dev/epoll code ?"
If yes, could you explain to me a case where /dev/epoll users have to fall back doing "plain-old-poll()" ?
- Davide
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |