From: Dan Kegel <dank@kegel.com>
To: Daniel McNeil <daniel@osdl.org>
Cc: "Eduardo Pérez" <100018135@alumnos.uc3m.es>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"linux-aio@kvack.org" <linux-aio@kvack.org>
Subject: Re: aio: current status
Date: Tue, 05 Aug 2003 15:19:07 -0700 [thread overview]
Message-ID: <3F302D5B.7050809@kegel.com> (raw)
In-Reply-To: <1060120389.14649.31.camel@ibm-c.pdx.osdl.net>
Daniel McNeil wrote:
> There was an interesting paper from the 2003 Linux Symposium on AIO:
> http://archive.linuxsymposium.org/ols2003/Proceedings/All-Reprints/Reprint-Pulavarty-OLS2003.pdf
Thanks for pointing that out. I now link to it from
http://www.kegel.com/c10k.html#aio
- Dan
--
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045
next prev parent reply other threads:[~2003-08-05 22:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 14:38 aio: current status Eduardo Pérez
2003-08-05 21:53 ` Daniel McNeil
2003-08-05 22:19 ` Dan Kegel [this message]
2003-08-06 13:25 ` Suparna Bhattacharya
2003-08-06 20:54 ` Daniel McNeil
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=3F302D5B.7050809@kegel.com \
--to=dank@kegel.com \
--cc=100018135@alumnos.uc3m.es \
--cc=daniel@osdl.org \
--cc=linux-aio@kvack.org \
--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