All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: Con Kolivas <kernel@kolivas.org>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.6.0 batch scheduling, HT aware
Date: Tue, 23 Dec 2003 13:40:41 +1100	[thread overview]
Message-ID: <3FE7AB29.7030502@cyberone.com.au> (raw)
In-Reply-To: <7F740D512C7C1046AB53446D372001736187E4@scsmsx402.sc.intel.com>



Nakajima, Jun wrote:

>Today utilization of execution resources of a logical processor is
>around 60% as you can find in public papers, and it's dependent on the
>processor implementation and the workload. It could be higher in the
>future, and their relative priority could be much higher then. So I
>don't think it's a good idea to hard code such a implementation-specific
>factor into the generic scheduler code.
>

No. The mechanism would be generic, but the parameters would be
arch specific as part of my sched domains patch (if I have anything
to do with it!)

>
>Regarding H/W-based priority, I'm not sure it's very useful especially
>because so many events happen inside the processor and a set of the
>execution resources required changes very rapidly at runtime, i.e. the
>H/W knows what it should do to run faster at runtime, and imposing
>priority on those logical processor could make them run slower.
>
>I think a software priority-based solution like the below would be more
>generic and work better.
>

I wouldn't pretend to know about hardware, but it seems like much nicer
than doing it in software. Anyway, if there is hardware out there without
priorities then it would be a good idea to code for it.

Nick


  reply	other threads:[~2003-12-23  2:40 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-23  1:59 [PATCH] 2.6.0 batch scheduling, HT aware Nakajima, Jun
2003-12-23  2:40 ` Nick Piggin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-23  5:33 Nakajima, Jun
2003-12-23 10:13 ` Nick Piggin
2003-12-23  0:38 Con Kolivas
2003-12-23  1:11 ` Nick Piggin
2003-12-23  1:24   ` Con Kolivas
2003-12-23  1:36     ` Nick Piggin
2003-12-23  2:42       ` Con Kolivas
2003-12-23  2:57         ` Nick Piggin
2003-12-23  3:15           ` Con Kolivas
2003-12-23  3:16             ` Con Kolivas
2003-12-26 23:03               ` Pavel Machek
2003-12-23 15:51           ` bill davidsen
2003-12-23 22:09             ` Con Kolivas
2003-12-30  0:35               ` bill davidsen
2004-01-02 20:10     ` Bill Davidsen
2003-12-26 22:56 ` Pavel Machek
2003-12-26 23:42   ` Con Kolivas
2003-12-26 23:49     ` Con Kolivas
2003-12-27 11:09     ` Pavel Machek
2003-12-27 11:15       ` Con Kolivas
2003-12-30  0:29         ` bill davidsen
2003-12-29  7:02       ` Nick Piggin
2003-12-29 12:49         ` Pavel Machek
2003-12-27  8:52   ` Mika Penttilä
2003-12-30  0:32     ` bill davidsen
2004-01-02 20:05   ` Bill Davidsen
2004-01-02 20:56     ` Davide Libenzi
2004-01-02 21:10       ` Valdis.Kletnieks
2004-01-02 23:34         ` Davide Libenzi

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=3FE7AB29.7030502@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=jun.nakajima@intel.com \
    --cc=kernel@kolivas.org \
    --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 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.