From: "David S. Miller" <davem@redhat.com>
To: frankeh@watson.ibm.com
Cc: lse-tech@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Patch and Performance of larger pipes
Date: Thu, 18 Oct 2001 10:43:23 -0700 (PDT) [thread overview]
Message-ID: <20011018.104323.26964897.davem@redhat.com> (raw)
In-Reply-To: <20011018113436.A9459@watson.ibm.com>
In-Reply-To: <20011018113436.A9459@watson.ibm.com>
Have you looked at all at the zerocopy pipe patches?
How do they affect the results, and by itself does it
do better than any of the schemes you propose?
Franks a lot,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-10-18 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-18 15:34 Patch and Performance of larger pipes Hubertus Franke
2001-10-18 17:43 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-18 18:07 Manfred Spraul
2001-10-18 18:18 ` Manfred Spraul
2001-10-18 23:05 ` Ryan Cumming
2001-10-19 0:15 ` Stefan Reinauer
2001-10-19 11:37 ` Carlo Strozzi
2001-10-19 4:19 ` Mike Galbraith
2001-10-19 13:52 ` Hubertus Franke
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=20011018.104323.26964897.davem@redhat.com \
--to=davem@redhat.com \
--cc=frankeh@watson.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
/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