From: Dan Kegel <dank@kegel.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Davide Libenzi <davidel@xmailserver.org>
Cc: Christopher Smith <x@xman.org>, Zach Brown <zab@zabbo.net>
Subject: Re: Could /dev/epoll deliver aio completion notifications? (was: Re: sigopen() vs. /dev/sigtimedwait)
Date: Fri, 03 Aug 2001 23:27:49 -0700 [thread overview]
Message-ID: <3B6B95E5.B49CC888@kegel.com> (raw)
In-Reply-To: <3B6B50C4.D9FBF398@kegel.com> <20010803183853.H1080@ppetru.net> <3B6B59AF.9826F928@kegel.com> <3B6B662F.3E83C22F@kegel.com> <20010804011838.W3034@erasmus.off.net>
Zach Brown wrote:
>
> > On the other hand, if /dev/epoll were flexible enough that it could
> > deliver AIO completion notifications,
>
> As far as I know, Ben LaHaise (bcrl@redhat.com) already has a fine
> method conceived for receiving batches of async completion, including an
> "async poll". It should give the sort of behaviour you want and is also
> useful for other AIO things, obviously :)
>
> You should really chat with him.
I suppose it shouldn't suprise me that real kernel hackers like Ben
just work on cool things quietly, and bufoons like me get excited
at the merest thought, and have to broadcast them on l-k. Sigh.
A little digging finds a few references to Ben's aio work:
http://uwsg.iu.edu/hypermail/linux/kernel/0102.0/0384.html
http://www.kvack.org/~blah/aio/v2.4.5-ac9-bcrl4-aio.diff
His patch creates /dev/aio, among other things, and includes
the wonderful excerpt
diff -urN /md0/kernels/2.4/v2.4.5-ac9/include/asm-i386/errno.h aio-2.4.5-ac9/include/asm-i386/errno.h
--- /md0/kernels/2.4/v2.4.5-ac9/include/asm-i386/errno.h Mon Feb 26 10:20:14 2001
+++ aio-2.4.5-ac9/include/asm-i386/errno.h Wed Jun 13 17:08:50 2001
@@ -128,5 +128,6 @@
#define ENOMEDIUM 123 /* No medium found */
#define EMEDIUMTYPE 124 /* Wrong medium type */
+#define ENOCLUE 125 /* userland programmer induced race condition */
:-)
Given how occupied Ben is with urgent matters like tracking down the
VM suckage, I don't expect he has much time for chatting about this stuff.
OK, guess I'll content myself with working through Ben's (and Davide's)
code and understanding it. Sorry for all the line noise, folks.
- Dan
--
"I have seen the future, and it licks itself clean." -- Bucky Katt
next prev parent reply other threads:[~2001-08-04 6:21 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 [this message]
2001-08-23 21:17 ` Could /dev/epoll deliver aio completion notifications? (was: 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=3B6B95E5.B49CC888@kegel.com \
--to=dank@kegel.com \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x@xman.org \
--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