From: Samium Gromoff <_deepfire@mail.ru>
To: mingo@elte.hu
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] scheduler cache affinity improvement in 2.4 kernels by Ingo Molnar
Date: Fri, 23 Nov 2001 14:47:06 +0300 (MSK) [thread overview]
Message-ID: <200111231147.fANBl7x11502@vegae.deep.net> (raw)
So as i see the patch in question is being hit in its weakest
place by that enormous 10 billion thread benchmark.
Indeed that weakest place is the added overhead which effects the
heavy scheduling load.
I look at it as at absolutely worst case. And even in this worst
case we still have a win on a 8-way smp... I`d like to see some
more real-life benchmarks on the issue...
Maybe the tester lose the point, cause the patch was not pointed
to improve the scheduling itself, but to reduce the loss of improper
scheduling - ie cache thrashing.
cheers, Samium Gromoff
next reply other threads:[~2001-11-23 11:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-23 11:47 Samium Gromoff [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-19 17:06 Shailabh Nagar
2001-11-17 16:58 Partha Narayanan
2001-11-17 17:21 ` Mark Hahn
2001-11-17 18:00 ` Alan Cox
2001-11-17 17:57 ` Arnaldo Carvalho de Melo
2001-11-19 8:39 ` Albert D. Cahalan
2001-11-23 11:48 ` 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=200111231147.fANBl7x11502@vegae.deep.net \
--to=_deepfire@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®