All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: "Li, Tong N" <tong.n.li@intel.com>,
	Giuseppe Bilotta <giuseppe.bilotta@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Re: [ANNOUNCE][RFC] PlugSched-6.5.1 for  2.6.22
Date: Mon, 16 Jul 2007 11:32:45 -0700	[thread overview]
Message-ID: <20070716183244.GC3318@linux-os.sc.intel.com> (raw)
In-Reply-To: <20070716065610.GA3653@stusta.de>

On Mon, Jul 16, 2007 at 08:56:10AM +0200, Adrian Bunk wrote:
> On Sun, Jul 15, 2007 at 10:03:02PM -0700, Li, Tong N wrote:
> > 
> > There are various metrics a scheduler may want to optimize for, such as
> > throughput, response time, power consumption, fairness, and so on. Each
> > of these may also be defined differently in different environments. Take
> > fairness as an example. People have traditionally talked about it in
> > terms of CPU time. Now it'd also make sense to talk about scheduling
> > that enables fair usage of other types of resources, such as shared
> > caches. Different metrics may require different scheduling policies.
> 
> Are these real-life problems people need solutions for today or just 
> thoughts someone might want to try and write a paper about?

We are at the door step of multi core evolution. So its a bit of both.

thanks,
suresh

  reply	other threads:[~2007-07-16 18:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-11 22:17 [ANNOUNCE][RFC] PlugSched-6.5.1 for 2.6.22 Al Boldi
2007-07-15  4:19 ` Giuseppe Bilotta
2007-07-15 17:47   ` Li, Tong N
2007-07-15 23:45     ` Adrian Bunk
2007-07-16  5:03       ` Li, Tong N
2007-07-16  6:56         ` Adrian Bunk
2007-07-16 18:32           ` Siddha, Suresh B [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-08-16 20:42 devzero

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=20070716183244.GC3318@linux-os.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=bunk@stusta.de \
    --cc=giuseppe.bilotta@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tong.n.li@intel.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.