From: Manfred Spraul <manfred@colorfullife.com>
To: Hubertus Franke <frankeh@watson.ibm.com>
Cc: lse-tech@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [Lse-tech] Re: Patch and Performance of larger pipes
Date: Tue, 30 Oct 2001 21:48:40 +0100 [thread overview]
Message-ID: <3BDF1228.E38185A1@colorfullife.com> (raw)
In-Reply-To: <OF2428DABF.B9AD95A4-ON86256AEA.005A4949@raleigh.ibm.com> <20011024153930.A12944@watson.ibm.com> <20011030133124.A16257@watson.ibm.com>
Hubertus Franke wrote:
>
> Manfred, here is some more performance measurement and comparision
> to round up some of the stuff we have been doing.
> It would be nice if you could make some comments. As usual raw numbers
> is not everything and there are other issues to consider.
> Comments ?
>
I'm that much interested at SMP performance right now - most of the SMP
problems are bad interactions with the scheduler. The current scheduler
and the pipe implementation are "optimized" for each other, e.g.
wake_up_sync() is IIRC exclusively used by pipes.
>
> UP
> --
> %imp
> R.Size W.Size R.Compute W.Compute 2.4.9.pipe Manfred
> ------ ------ ------------------- ---------- --------------
> 512 32k 500 0 0 1.04
> 512 32k 0 500 -0.91 7.72
>
> 32k 512 500 0 1.09 -78.3
> 32k 512 0 500 0 0
>
I'll try to check that one ASAP. An uniprocessor performance degration
points to an implementation bug in my code.
--
Manfred
next prev parent reply other threads:[~2001-10-30 20:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF2428DABF.B9AD95A4-ON86256AEA.005A4949@raleigh.ibm.com>
2001-10-24 19:39 ` [Lse-tech] Re: Patch and Performance of larger pipes Hubertus Franke
2001-10-30 18:31 ` Hubertus Franke
2001-10-30 20:48 ` Manfred Spraul [this message]
2001-11-03 17:39 ` Manfred Spraul
2001-11-05 14:11 ` 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=3BDF1228.E38185A1@colorfullife.com \
--to=manfred@colorfullife.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