From: Robert Love <rml@tech9.net>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: linux-kernel@vger.kernel.org, nigel@nrg.org
Subject: Re: Updated Linux kernel preemption patches
Date: 26 Aug 2001 23:09:49 -0400 [thread overview]
Message-ID: <998881793.805.30.camel@phantasy> (raw)
In-Reply-To: <20010827025934Z16098-32383+1547@humbolt.nl.linux.org>
In-Reply-To: <998877465.801.19.camel@phantasy> <20010827025934Z16098-32383+1547@humbolt.nl.linux.org>
On Sun, 2001-08-26 at 23:06, Daniel Phillips wrote:
> Congratulations on showing evidence that preemption can improve performance
> under some loads, especially the all-important kernel compile. Don't be too
> worried about the dbench 1 results, dbench can vary by a factor of 2
> depending on the alignment of the planets (ask Tridge). Try something more
> stable like bonnie.
I would be happy to run some other tests. I was happy to see the kernel
compile prove faster, and I fully expected the dbench 16 results to show
an improvement. But, while I assumed dbench 1 may show a degradation in
performance, I was surprised it was so high.
My main goal in updating Nigel's patches to recent kernels was to
accomplish just this: get some more data points, some more benchmarks,
and more eyes on the code and systems running the patch.
I am not an audio guy or otherwise in need of a lower-latency system,
but the possibility for an overall improvement in the kernel (even at
the expense of some cases) is worthwhile, to me.
> The theory goes that preemption improves performance by cutting down the time
> between IO completion and user task resume, with only a small cost in extra
> locking. It would be nice to see profiling statistics to support this idea.
Anyone running the patch want to profile some situations and reach some
conclusions?
--
Robert M. Love
rml at ufl.edu
rml at tech9.net
next prev parent reply other threads:[~2001-08-27 3:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-27 1:57 Updated Linux kernel preemption patches Robert Love
2001-08-27 3:06 ` Daniel Phillips
2001-08-27 3:09 ` Robert Love [this message]
2001-08-27 7:38 ` Cliff Albert
2001-08-27 13:46 ` Robert Love
2001-08-27 15:20 ` Cliff Albert
2001-08-27 19:31 ` J Sloan
2001-08-27 19:44 ` Robert Love
2001-08-27 21:12 ` Andrey Nekrasov
2001-08-27 21:35 ` Robert Love
2001-08-27 21:18 ` Robert Love
2001-08-27 21:24 ` Cliff Albert
2001-08-27 21:40 ` Robert Love
2001-08-27 23:06 ` Andrey Nekrasov
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=998881793.805.30.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nigel@nrg.org \
--cc=phillips@bonn-fries.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