From: Carlo Wood <carlo@alinoe.com>
To: Dan Kegel <dank@kegel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: kqueue, kevent - kernel event notification mechanism
Date: Thu, 6 Dec 2001 15:28:36 +0100 [thread overview]
Message-ID: <20011206152836.A22005@alinoe.com> (raw)
In-Reply-To: <3C0F1F32.C235F9CC@kegel.com>
In-Reply-To: <3C0F1F32.C235F9CC@kegel.com>; from dank@kegel.com on Wed, Dec 05, 2001 at 11:33:06PM -0800
On Wed, Dec 05, 2001 at 11:33:06PM -0800, Dan Kegel wrote:
> See http://www.kegel.com/c10k.html#nb.sigio for details.
Wow! Thanks for writing that *wonderful* page!!! That is
exactly the documentation I was looking for to improve my
'An Object Oriented Core library for Event Driven Applications'
library (http://libcw.sourceforge.net/), a library intended
for Heavy Duty networking applications that I've been working
on for the past few years.
Thanks!
--
Carlo Wood <carlo@alinoe.com>
next prev parent reply other threads:[~2001-12-06 14:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 7:33 kqueue, kevent - kernel event notification mechanism Dan Kegel
2001-12-06 14:28 ` Carlo Wood [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-06 0:38 Carlo Wood
2001-12-06 0:57 ` Alan Cox
2001-12-06 5:48 ` Benjamin LaHaise
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=20011206152836.A22005@alinoe.com \
--to=carlo@alinoe.com \
--cc=dank@kegel.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