From: rwhron@earthlink.net
To: linux-kernel@vger.kernel.org
Cc: kravetz@us.ibm.com, jamagallon@able.es, rml@tech9.net
Subject: Re: O(1) scheduler gives big boost to tbench 192
Date: Mon, 20 May 2002 08:46:11 -0400 [thread overview]
Message-ID: <20020520084611.A14924@rushmore> (raw)
> On Tue, May 07, 2002 at 04:39:34PM -0700, Robert Love wrote:
> > It is just for pipes we previously used sync, no?
On Tue, 7 May 2002 16:48:57 -0700, Mike Kravetz wrote
> That's the only thing I know of that used it.
> I'd really like to know if there are any real workloads that
> benefited from this feature, rather than just some benchmark.
> I can do some research, but was hoping someone on this list
> might remember. If there is a valid workload, I'll propose
> a patch.
On Mon, 13 May 2002 02:06:31 +0200, J.A. Magallon wrote:
> - Re-introduction of wake_up_sync to make pipes run fast again. No idea
> about this is useful or not, that is the point, to test it
2.4.19-pre8-jam2 showed slightly better performance on the quad Xeon
for most benchmarks with 25-wake_up_sync backed out. However, it's
not clear to me 25-wake_up_sync was proper patch to backout for this
test, as there wasn't a dramatic change in Pipe latency or bandwidth
without it.
There was a > 300% improvement lmbench Pipe bandwidth and latency
comparing pre8-jam2 to pre7-jam6.
Average of 25 lmbench runs on jam2 kernels, 12 on the others:
2.4.19-pre8-jam2-nowuos (backed out 25-wake_up_sync patch)
*Local* Communication latencies in microseconds - smaller is better
AF
kernel Pipe UNIX
----------------------- ----- -----
2.4.19-pre7-jam6 29.51 42.37
2.4.19-pre8 10.73 29.94
2.4.19-pre8-aa2 12.45 29.53
2.4.19-pre8-ac1 35.39 45.59
2.4.19-pre8-jam2 7.70 15.27
2.4.19-pre8-jam2-nowuos 7.74 14.93
*Local* Communication bandwidths in MB/s - bigger is better
AF
kernel Pipe UNIX
----------------------- ------ ------
2.4.19-pre7-jam6 66.41 260.39
2.4.19-pre8 468.57 273.32
2.4.19-pre8-aa2 418.09 273.59
2.4.19-pre8-ac1 110.62 241.06
2.4.19-pre8-jam2 545.66 233.68
2.4.19-pre8-jam2-nowuos 544.57 246.53
The kernel build test, which applies patches through a pipe
and compiles with -pipe didn't reflect an improvement.
kernel average min_time max_time runs notes
2.4.19-pre7-jam6 237.0 235 239 3 All successful
2.4.19-pre8 239.7 238 241 3 All successful
2.4.19-pre8-aa2 237.7 237 238 3 All successful
2.4.19-pre8-ac1 239.3 238 241 3 All successful
2.4.19-pre8-jam2 240.0 238 241 3 All successful
2.4.19-pre8-jam2-nowuos 238.7 236 241 3 All successful
I don't know how much of the kernel build test is dependant on
pipe performance. There is probably a better "real world"
measurement.
On a single processor box, there was an improvement on kernel build
between pre7-jam6 and pre8-jam2. That was only on one sample though.
Xeon page:
http://home.earthlink.net/~rwhron/kernel/bigbox.html
Latest on uniproc:
http://home.earthlink.net/~rwhron/kernel/latest.html
--
Randy Hron
next reply other threads:[~2002-05-20 12:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-20 12:46 rwhron [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-08 16:39 O(1) scheduler gives big boost to tbench 192 Bill Davidsen
2002-05-06 8:20 rwhron
2002-05-06 16:42 ` Andrea Arcangeli
2002-05-03 16:37 John Hawkes
2002-05-03 13:38 rwhron
2002-05-03 20:29 ` Gerrit Huizenga
2002-05-04 8:13 ` Andrea Arcangeli
2002-05-07 22:13 ` Mike Kravetz
2002-05-07 22:44 ` Alan Cox
2002-05-07 22:43 ` Mike Kravetz
2002-05-07 23:39 ` Robert Love
2002-05-07 23:48 ` Mike Kravetz
2002-05-08 15:34 ` Jussi Laako
2002-05-08 16:31 ` Robert Love
2002-05-08 17:02 ` Mike Kravetz
2002-05-09 0:26 ` Jussi Laako
2002-05-08 8:50 ` Andrea Arcangeli
2002-05-09 23:18 ` Mike Kravetz
2002-05-02 21:36 rwhron
2002-05-03 0:09 ` Gerrit Huizenga
2002-05-02 23:17 ` J.A. Magallon
2002-05-03 0:14 ` Alan Cox
2002-05-03 1:08 ` Gerrit Huizenga
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=20020520084611.A14924@rushmore \
--to=rwhron@earthlink.net \
--cc=jamagallon@able.es \
--cc=kravetz@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.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