public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin LaHaise <bcrl@redhat.com>
To: Hubertus Franke <frankeh@watson.ibm.com>
Cc: Manfred Spraul <manfred@colorfullife.com>,
	linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net
Subject: Re: [Lse-tech] zerocopy pipe, new version
Date: Tue, 15 Jan 2002 14:57:47 -0500	[thread overview]
Message-ID: <20020115145747.F6853@redhat.com> (raw)
In-Reply-To: <002701c19638$400f15f0$010411ac@local> <011001c19de8$ec1d4800$1cdb0209@diz.watson.ibm.com>
In-Reply-To: <011001c19de8$ec1d4800$1cdb0209@diz.watson.ibm.com>; from frankeh@watson.ibm.com on Tue, Jan 15, 2002 at 12:20:25PM -0500

On Tue, Jan 15, 2002 at 12:20:25PM -0500, Hubertus Franke wrote:
> Conclusion
> ----------
> Manfred Spraul's new zero copy patch showed a very good performance
> improvement for pipeflex as well as grep on both 2-way and 1-way.
> By adding our large pipe support, performance improvement up to
> 42% for pipeflex and 96% for grep benchmarks on 2-way systems.
> No significant different has been observed for lmbench on 1-way systems.
> The right way to configure the system than would be for UP and 1-way to
> set the buffer size by default to 4K while for the SMP larger pipe buffers
> should be encouraged.

Any conclusions are incomplete without mentioning the serious (30%+) 
degredation on UP systems under a good chunk of the benchmarks.  Such 
aspects of the patch make it unsuitable as is for both the mainstream 
and vendor kernels.

		-ben

  reply	other threads:[~2002-01-15 19:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-05 22:27 zerocopy pipe, new version Manfred Spraul
2002-01-15 17:20 ` [Lse-tech] " Hubertus Franke
2002-01-15 19:57   ` Benjamin LaHaise [this message]
2002-01-15 20:08     ` Manfred Spraul
2002-01-15 20:20       ` Benjamin LaHaise
2002-01-16 15:29         ` 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=20020115145747.F6853@redhat.com \
    --to=bcrl@redhat.com \
    --cc=frankeh@watson.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=manfred@colorfullife.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