From: Benjamin LaHaise <bcrl@redhat.com>
To: Simon Kirby <sim@netnation.com>
Cc: Matti Aarnio <matti.aarnio@zmailer.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
linux-kernel@vger.kernel.org
Subject: Re: O_NONBLOCK on files
Date: Mon, 24 Sep 2001 17:30:29 -0400 [thread overview]
Message-ID: <20010924173029.J17683@redhat.com> (raw)
In-Reply-To: <20010918234648.A21010@netnation.com> <m1r8t3fyot.fsf@frodo.biederman.org> <20010919002439.A21138@netnation.com> <20010924234717.V11046@mea-ext.zmailer.org> <20010924140534.E2335@netnation.com>
In-Reply-To: <20010924140534.E2335@netnation.com>; from sim@netnation.com on Mon, Sep 24, 2001 at 02:05:34PM -0700
On Mon, Sep 24, 2001 at 02:05:34PM -0700, Simon Kirby wrote:
> Yes, but this sucks. My whole intent was an interface design that would
> never need to context switch. I'm not sure if this is even possible, but
> if so it would be very nice from a userspace perspective.
Actually, this was one of the design concerns that I had in coming up with
the async io interfaces. The interface was designed to make use of the
upcoming syscalls-in-userspace stubs that x86-64 implemented and will be
passed on to x86 in 2.5. All completion events are passed through a ring
buffer with minimal locking on the kernel side which only needs thread
locking in userspace. This way the whole userspace to kernel transition
can be avoided by the server under sufficiently high load.
-ben
next prev parent reply other threads:[~2001-09-24 21:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-19 6:46 O_NONBLOCK on files Simon Kirby
2001-09-19 7:05 ` Eric W. Biederman
2001-09-19 7:24 ` Simon Kirby
2001-09-24 20:47 ` Matti Aarnio
2001-09-24 21:05 ` Simon Kirby
2001-09-24 21:30 ` Benjamin LaHaise [this message]
2001-09-19 8:52 ` Erik Andersen
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=20010924173029.J17683@redhat.com \
--to=bcrl@redhat.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.aarnio@zmailer.org \
--cc=sim@netnation.com \
/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