From: Dan Kegel <dank@alumni.caltech.edu>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Kiobuf-io-devel] Re: RFC: Kernel mechanism: Compound event wait/notify + callback chains
Date: Wed, 31 Jan 2001 10:38:50 -0800 [thread overview]
Message-ID: <3A785BBA.55AC2B65@alumni.caltech.edu> (raw)
sct wrote:
> On Wed, Jan 31, 2001 at 04:12:11PM +0530, bsuparna@in.ibm.com wrote:
> >
> > Thanks for mentioning this. I didn't know about it earlier. I've been
> > going through the 4/00 kqueue patch on freebsd ...
>
> Linus has already denounced them as massively over-engineered...
That shouldn't stop anyone from looking at them and learning, though.
There might be a good idea or two hiding in there somewhere.
- Dan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-31 18:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 18:38 Dan Kegel [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-31 10:42 [Kiobuf-io-devel] Re: RFC: Kernel mechanism: Compound event wait/notify + callback chains bsuparna
2001-01-31 11:26 ` Stephen C. Tweedie
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=3A785BBA.55AC2B65@alumni.caltech.edu \
--to=dank@alumni.caltech.edu \
--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