From: Davide Libenzi <davidel@xmailserver.org>
To: "Christopher K. St. John" <cks@distributopia.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: /dev/yapoll : Re: [PATCH] /dev/epoll update ...
Date: Fri, 21 Sep 2001 14:36:23 -0700 (PDT) [thread overview]
Message-ID: <XFMail.20010921143623.davidel@xmailserver.org> (raw)
In-Reply-To: <3BABA15A.57255E63@distributopia.com>
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
next prev parent reply other threads:[~2001-09-21 21:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-21 6:22 [PATCH] /dev/epoll update Dan Kegel
2001-09-21 18:45 ` Davide Libenzi
2001-09-21 19:40 ` /dev/yapoll : " Christopher K. St. John
2001-09-21 20:10 ` Davide Libenzi
2001-09-21 20:21 ` Christopher K. St. John
2001-09-21 21:36 ` Davide Libenzi [this message]
2001-09-21 21:33 ` Christopher K. St. John
2001-09-21 21:52 ` Davide Libenzi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=XFMail.20010921143623.davidel@xmailserver.org \
--to=davidel@xmailserver.org \
--cc=cks@distributopia.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.