From: John Gardiner Myers <jgmyers@netscape.com>
To: linux-aio <linux-aio@kvack.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] adding aio_readv/writev
Date: Tue, 24 Sep 2002 07:13:39 -0700 [thread overview]
Message-ID: <3D907313.8040704@netscape.com> (raw)
In-Reply-To: 20020924145225.J3160@redhat.com
[-- Attachment #1: Type: text/plain, Size: 640 bytes --]
Stephen C. Tweedie wrote:
>No, all you can infer from that is that "some method for avoiding
>small packets is important for networking." TCP_CORK already does
>that in Linux, for tcp at least, without requiring writev. (Of
>course, normal nonblocking writev is still there if you want it.)
>
TCP_CORK is indeed effective for avoiding small packets. Be that as it
may, the source data for network writes are frequently in discontiguous
buffers and writev is nonetheless still important for networking. The
alternative in the aio model is to waste a lot of resources delivering
io completions the application doesn't care about.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3537 bytes --]
next prev parent reply other threads:[~2002-09-24 14:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-20 20:39 [RFC] adding aio_readv/writev Shailabh Nagar
[not found] ` <1032555981.2082.10.camel@dell_ss3.pdx.osdl.net>
2002-09-23 14:30 ` Shailabh Nagar
2002-09-23 18:53 ` Clement T. Cole
[not found] ` <20020923114104.A11680@redhat.com>
2002-09-24 13:20 ` John Gardiner Myers
2002-09-24 13:52 ` Stephen C. Tweedie
2002-09-24 14:13 ` John Gardiner Myers [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-23 17:59 Chen, Kenneth W
[not found] <200209231851.g8NIpea12782@igw2.watson.ibm.com>
2002-09-23 19:52 ` Shailabh Nagar
2002-09-23 20:39 ` Clement T. Cole
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=3D907313.8040704@netscape.com \
--to=jgmyers@netscape.com \
--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