From: Benjamin LaHaise <bcrl@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Carlo Wood <carlo@alinoe.com>, linux-kernel@vger.kernel.org
Subject: Re: kqueue, kevent - kernel event notification mechanism
Date: Thu, 6 Dec 2001 00:48:48 -0500 [thread overview]
Message-ID: <20011206004848.C29061@redhat.com> (raw)
In-Reply-To: <20011206013857.A17313@alinoe.com> <E16Bmqo-0008Fj-00@the-village.bc.nu>
In-Reply-To: <E16Bmqo-0008Fj-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Thu, Dec 06, 2001 at 12:57:21AM +0000
On Thu, Dec 06, 2001 at 12:57:21AM +0000, Alan Cox wrote:
> The API isnt directly the problem. In fact you can make a fine scalable select
> by implementing
>
> poll_setup(..............)
> poll_add/poll_remove
> poll_wait
>
> as multiple calls giving basically the same interface that apps expected
> anyway. Take a look at the various /dev/poll experimental interfaces and
> bits of code.
My aio patches already have a poll operation, however it acts as a one shot
operation: an async poll does not complete until the state indicates
readiness or it is cancelled. That's needed as there is a 1-1 relationship
between submitted aio operations and the space in the completion ring. Still,
it looks like it will work quite nicely as a means of accelerating exiting
poll() based servers.
-ben
-ben
next prev parent reply other threads:[~2001-12-06 5:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 0:38 kqueue, kevent - kernel event notification mechanism Carlo Wood
2001-12-06 0:57 ` Alan Cox
2001-12-06 5:48 ` Benjamin LaHaise [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-06 7:33 Dan Kegel
2001-12-06 14:28 ` Carlo Wood
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=20011206004848.C29061@redhat.com \
--to=bcrl@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=carlo@alinoe.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox