public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: John Gardiner Myers <jgmyers@netscape.com>
Cc: linux-aio <linux-aio@kvack.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] adding aio_readv/writev
Date: Tue, 24 Sep 2002 14:52:25 +0100	[thread overview]
Message-ID: <20020924145225.J3160@redhat.com> (raw)
In-Reply-To: <3D9066AD.6030904@netscape.com>; from jgmyers@netscape.com on Tue, Sep 24, 2002 at 06:20:45AM -0700

Hi,

On Tue, Sep 24, 2002 at 06:20:45AM -0700, John Gardiner Myers wrote:
 
> Benjamin LaHaise wrote:
> 
> >Only db2 uses vectored io heavily.  Oracle does not, and none of the open 
> >source databases do.  Vectored io is pretty useless for most people.
> >  
> >
> writev is extremely important for networking as it avoids small packets.

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.)

--Stephen

  reply	other threads:[~2002-09-24 13:47 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 [this message]
2002-09-24 14:13           ` John Gardiner Myers
  -- 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=20020924145225.J3160@redhat.com \
    --to=sct@redhat.com \
    --cc=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