All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Ingo Molnar <mingo@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] HT scheduler, sched-2.5.68-A9
Date: Tue, 22 Apr 2003 05:01:17 +0100	[thread overview]
Message-ID: <20030422040117.GA31324@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0304211509010.11700-100000@devserv.devel.redhat.com>

On Mon, Apr 21, 2003 at 03:13:31PM -0400, Ingo Molnar wrote:

 > +/*
 > + * Is there a way to do this via Kconfig?
 > + */
 > +#if CONFIG_NR_SIBLINGS_2
 > +# define CONFIG_NR_SIBLINGS 2
 > +#elif CONFIG_NR_SIBLINGS_4
 > +# define CONFIG_NR_SIBLINGS 4
 > +#else
 > +# define CONFIG_NR_SIBLINGS 0
 > +#endif
 > +

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.

 > +#if CONFIG_NR_SIBLINGS
 > +# define CONFIG_SHARE_RUNQUEUE 1
 > +#else
 > +# define CONFIG_SHARE_RUNQUEUE 0
 > +#endif

And why can't this just be a

	if (ht_enabled)
		shared_runqueue = 1;

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.

		Dave

  reply	other threads:[~2003-04-22  3:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-21 19:13 [patch] HT scheduler, sched-2.5.68-A9 Ingo Molnar
2003-04-22  4:01 ` Dave Jones [this message]
2003-04-22  7:08   ` Ingo Molnar
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=20030422040117.GA31324@suse.de \
    --to=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.