From: Hubertus Franke <frankeh@watson.ibm.com>
To: Benjamin LaHaise <bcrl@redhat.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: Wed, 16 Jan 2002 10:29:54 -0500 [thread overview]
Message-ID: <20020116102954.A1241@elinux01.watson.ibm.com> (raw)
In-Reply-To: <002701c19638$400f15f0$010411ac@local> <011001c19de8$ec1d4800$1cdb0209@diz.watson.ibm.com> <20020115145747.F6853@redhat.com> <001801c19e00$71c355a0$010411ac@local> <20020115152038.G6853@redhat.com>
In-Reply-To: <20020115152038.G6853@redhat.com>; from bcrl@redhat.com on Tue, Jan 15, 2002 at 03:20:38PM -0500
On Tue, Jan 15, 2002 at 03:20:38PM -0500, Benjamin LaHaise wrote:
> On Tue, Jan 15, 2002 at 09:08:45PM +0100, Manfred Spraul wrote:
> > My patch is definitively WIP - right now I again broke the -ENOMEM and
> > -EFAULT handling.
>
> I am aware of that, but the lse-tech posting made it sound as if things are
> great now since the SMP numbers improved. Please folks, remember that UP
> numbers are important too.
>
> -ben
> --
> Fish.
Ben, yes you are right, the lse-posting in a second reading is misleading.
As reported previously http://lse.sourceforge.net/pipe/pipe-report
UP numbers see degradations for LM-Bench, other benchmarks are OK.
This is not solved either by an integration of zero-copy with large pipes.
We have however shown that the for SMP systems adding larger pipes to
zero-copy pipes makes sense and for UP and 1-way sticking with a 1-page
pipe does not degradate Manfred's patch.
It hence boils down to a proper parameterization of the pipe dependent on
the configuration.
-- Hubertus
prev parent reply other threads:[~2002-01-16 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-05 22:27 Manfred Spraul
2002-01-15 17:20 ` [Lse-tech] " Hubertus Franke
2002-01-15 19:57 ` Benjamin LaHaise
2002-01-15 20:08 ` Manfred Spraul
2002-01-15 20:20 ` Benjamin LaHaise
2002-01-16 15:29 ` Hubertus Franke [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=20020116102954.A1241@elinux01.watson.ibm.com \
--to=frankeh@watson.ibm.com \
--cc=bcrl@redhat.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
all inboxes | Powered by JetHome®