From: Ingo Molnar <mingo@redhat.com>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] HT scheduler, sched-2.5.68-A9
Date: Tue, 22 Apr 2003 03:08:27 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0304220305260.25143-100000@devserv.devel.redhat.com> (raw)
In-Reply-To: <20030422040117.GA31324@suse.de>
On Tue, 22 Apr 2003, Dave Jones wrote:
> Maybe this would be better resolved at runtime ? With the above patch,
> you'd need three seperate kernel images to run optimally on a system in
> each of the cases. The 'vendor kernel' scenario here looks ugly to me.
it's not a problem - vendors enable it and that's all. But the majority of
SMP systems does not need a shared runqueue, so the associated overhead
(which, while small, is nonzero) can be avoided.
> Dumping all this into the config system seems to be the wrong direction
> IMHO. The myriad of runtime knobs in the scheduler already is bad
> enough, without introducing compile time ones as well.
what runtime knobs? I've avoided as many of them as possible.
Ingo
next prev parent reply other threads:[~2003-04-22 6:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-21 19:13 Ingo Molnar
2003-04-22 4:01 ` Dave Jones
2003-04-22 7:08 ` Ingo Molnar [this message]
2003-04-22 10:18 ` Rick Lindsley
2003-04-22 10:34 ` Ingo Molnar
2003-04-22 11:10 ` Rick Lindsley
2003-04-22 11:27 ` Ingo Molnar
2003-04-22 22:16 ` several messages Bill Davidsen
2003-04-22 23:38 ` Rick Lindsley
2003-04-23 9:17 ` Ingo Molnar
2003-04-22 23:48 ` [patch] HT scheduler, sched-2.5.68-A9 Martin J. Bligh
2003-04-23 9:12 ` 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=Pine.LNX.4.44.0304220305260.25143-100000@devserv.devel.redhat.com \
--to=mingo@redhat.com \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®