From: John Gardiner Myers <jgmyers@netscape.com>
To: Benjamin LaHaise <bcrl@redhat.com>
Cc: linux-aio@kvack.org, linux-kernel@vger.kernel.org,
torvalds@transmeta.com
Subject: Re: [PATCH] aio updates
Date: Tue, 15 Oct 2002 15:08:12 -0700 [thread overview]
Message-ID: <3DAC91CC.5000202@netscape.com> (raw)
In-Reply-To: 20021015173153.G16156@redhat.com
[-- Attachment #1: Type: text/plain, Size: 299 bytes --]
Benjamin LaHaise wrote:
>non-file descriptor consuming operations should most likely
>be their own syscalls (imho).
>
This would defeat the multiple iocb submission feature of io_submit().
All async operations should be submittable through io_submit() to
permit multiple operation submission.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3537 bytes --]
prev parent reply other threads:[~2002-10-15 22:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 1:17 [PATCH] aio updates John Myers
2002-10-15 19:57 ` Benjamin LaHaise
2002-10-15 20:50 ` John Gardiner Myers
2002-10-15 21:31 ` Benjamin LaHaise
2002-10-15 22:05 ` John Gardiner Myers
2002-10-15 22:08 ` John Gardiner Myers [this message]
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=3DAC91CC.5000202@netscape.com \
--to=jgmyers@netscape.com \
--cc=bcrl@redhat.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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