From: Jussi Laako <jussi.laako@kolumbus.fi>
To: mingo@elte.hu
Cc: Ed Tomlinson <tomlins@cam.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] improving O(1)-J9 in heavily threaded situations
Date: Tue, 05 Feb 2002 00:56:17 +0200 [thread overview]
Message-ID: <3C5F1191.D90D7556@kolumbus.fi> (raw)
In-Reply-To: <Pine.LNX.4.33.0202042303240.16086-100000@localhost.localdomain>
Ingo Molnar wrote:
>
> please give it a test then (i'd suggest using the latest, -K2 patch) and
> let me know about what you find - this way we can fix any possible real
> problems instead of talking in hypotheticals.
I've been testing all your scheduler versions since first one.
Ok, now I made comparison test with exactly same kernel except other one
with -K2 patch. O1-K2 behaves significantly worse than old scheduler. I
think this behaviour was introduced somewhere around beginning of -J series.
I can't make kernel with old scheduler loose datablocks, but with O1 it
looses large percentage of the blocks.
- Jussi Laako
--
PGP key fingerprint: 161D 6FED 6A92 39E2 EB5B 39DD A4DE 63EB C216 1E4B
Available at PGP keyservers
next prev parent reply other threads:[~2002-02-04 22:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0202040627001.22583-100000@localhost.localdomain>
2002-02-04 4:40 ` [PATCH] improving O(1)-J9 in heavily threaded situations Ed Tomlinson
2002-02-04 12:30 ` Ingo Molnar
2002-02-04 12:36 ` Ingo Molnar
2002-02-04 10:47 ` Arjan van de Ven
2002-02-04 14:09 ` Ingo Molnar
2002-02-04 12:18 ` Ed Tomlinson
2002-02-04 20:01 ` Jussi Laako
2002-02-04 22:06 ` Ingo Molnar
2002-02-04 22:56 ` Jussi Laako [this message]
2002-02-05 0:56 ` Ingo Molnar
2002-02-04 23:32 ` Jussi Laako
2002-02-05 1:34 ` Ingo Molnar
2002-02-04 22:24 ` Bill Davidsen
2002-02-04 12:32 Ed Tomlinson
2002-02-04 12:33 ` Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2002-02-03 6:00 Ed Tomlinson
2002-02-02 15:50 Ed Tomlinson
2002-02-03 11:32 ` Ingo Molnar
2002-02-03 15:46 ` Ed Tomlinson
2002-02-04 0:46 ` Ingo Molnar
2002-02-04 19:52 ` Jussi Laako
2002-02-05 0:59 ` Ingo Molnar
2002-02-04 23:36 ` Jussi Laako
2002-02-05 1:37 ` Ingo Molnar
2002-02-06 0:43 ` Jussi Laako
2002-02-06 12:37 ` Ingo Molnar
2002-02-07 1:10 ` Jussi Laako
2002-02-07 22:28 ` Ingo Molnar
2002-02-10 15:00 ` Jussi Laako
2002-02-05 1:41 ` Ingo Molnar
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=3C5F1191.D90D7556@kolumbus.fi \
--to=jussi.laako@kolumbus.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tomlins@cam.org \
/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