From: Davide Libenzi <davidel@xmailserver.org>
To: Dan Kegel <dank@kegel.com>
Cc: Zach Brown <zab@zabbo.net>
Cc: Zach Brown <zab@zabbo.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Christopher Smith <x@xman.org>, Petru Paler <ppetru@ppetru.net>
Subject: RE: Could /dev/epoll deliver aio completion notifications? (was:
Date: Thu, 23 Aug 2001 14:17:14 -0700 (PDT) [thread overview]
Message-ID: <XFMail.20010823141714.davidel@xmailserver.org> (raw)
In-Reply-To: <3B6B662F.3E83C22F@kegel.com>
On 04-Aug-2001 Dan Kegel wrote:
> Davide, is that along the lines of what you were thinking of
> for /dev/epoll and disk files? (Plain old polling of disk
> files doesn't make much sense unless you're just interested in
> them growing, I suppose; aio completion notification is what you
> really want.)
Dan, sorry for the response delay but I was in Vacation Mode ( new CPU execution mode
that will be included in the next x86 generation ).
I trashed my original idea to extend /dev/epoll to other other files coz this will make the
patch way more intrusive. The only easy extension that comes in my mind is pipes.
As soon as I'll finish to read the remaining 4231 messages in my mbox I'll fix /dev/epoll
to get rid of stale events that I ( and Erich Nahum ) noticed in the current implementation.
- Davide
prev parent reply other threads:[~2001-08-23 21:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-04 1:32 sigopen() vs. /dev/sigtimedwait Dan Kegel
2001-08-04 1:38 ` Petru Paler
2001-08-04 2:10 ` Dan Kegel
2001-08-04 3:04 ` Could /dev/epoll deliver aio completion notifications? (was: Re: sigopen() vs. /dev/sigtimedwait) Dan Kegel
2001-08-04 5:18 ` Zach Brown
2001-08-04 6:27 ` Dan Kegel
2001-08-23 21:17 ` Davide Libenzi [this message]
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.20010823141714.davidel@xmailserver.org \
--to=davidel@xmailserver.org \
--cc=dank@kegel.com \
--cc=zab@zabbo.net \
/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