All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Snook <csnook@redhat.com>
To: "Li, Tong N" <tong.n.li@intel.com>
Cc: Chris Friesen <cfriesen@nortel.com>,
	mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [RFC] scheduler: improve SMP fairness in CFS
Date: Tue, 24 Jul 2007 17:09:28 -0400	[thread overview]
Message-ID: <46A66A88.8070307@redhat.com> (raw)
In-Reply-To: <1185310691.7737.40.camel@tongli.jf.intel.com>

Li, Tong N wrote:
> On Tue, 2007-07-24 at 16:39 -0400, Chris Snook wrote:
> 
>> Divining the intentions of the administrator is an AI-complete problem and we're 
>> not going to try to solve that in the kernel.  An intelligent administrator 
>> could also allocate 50% of each CPU to a resource group containing all the 
>> *other* processes.  Then, when the other processes are scheduled out, your 
>> single task will run on whichever CPU is idle.  This will very quickly 
>> equilibrate to the scheduling ping-pong you seem to want.  The scheduler 
>> deliberately avoids this kind of migration by default because it hurts cache and 
>> TLB performance, so if you want to override this very sane default behavior, 
>> you're going to have to explicitly configure it yourself.
>>
> 
> Well, the admin wouldn't specifically ask for 50% of each CPU. He would
> just allocate 50% of total CPU time---it's up to the scheduler to
> fulfill that. If a task is entitled to one CPU, then it'll stay there
> and have no migration. Migration occurs only if there's overload, in
> which case I think you agree in your last email that the cache and TLB
> impact is not an issue (at least in SMP).

I don't think Chris's scenario has much bearing on your patch.  What he wants is 
to have a task that will always be running, but can't monopolize either CPU. 
This is useful for certain realtime workloads, but as I've said before, realtime 
requires explicit resource allocation.  I don't think this is very relevant to 
SCHED_FAIR balancing.

	-- Chris

  reply	other threads:[~2007-07-24 21:09 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-23 18:38 [RFC] scheduler: improve SMP fairness in CFS Tong Li
2007-07-23 20:00 ` Andi Kleen
2007-07-23 21:10   ` Li, Tong N
2007-07-23 21:25     ` Chris Friesen
2007-07-24  9:43       ` Andi Kleen
2007-07-23 23:40 ` Chris Snook
2007-07-24  8:07   ` Chris Snook
2007-07-24 17:11     ` Li, Tong N
2007-07-24 17:07   ` Tong Li
2007-07-24 18:08     ` Chris Snook
2007-07-24 19:47       ` Chris Friesen
2007-07-24 20:39         ` Chris Snook
2007-07-24 20:58           ` Li, Tong N
2007-07-24 21:09             ` Chris Snook [this message]
2007-07-24 21:23               ` Chris Friesen
2007-07-24 21:45                 ` Chris Snook
2007-07-24 23:33                   ` Chris Friesen
2007-07-24 21:06           ` Bill Huey
2007-07-24 21:22             ` Chris Snook
2007-07-24 23:14               ` Bill Huey
2007-07-24 21:12           ` Chris Friesen
2007-07-25 11:01 ` Ingo Molnar
2007-07-25 12:03   ` Ingo Molnar
2007-07-25 17:23     ` Tong Li
2007-07-25 19:24       ` Ingo Molnar
2007-07-25 20:38         ` Chris Friesen
2007-07-25 20:55           ` Chris Snook
2007-07-25 21:15             ` Li, Tong N
2007-07-25 22:24               ` Chris Snook
2007-07-26 19:00         ` Tong Li
2007-07-26 21:31           ` Ingo Molnar
2007-07-26 22:00             ` Li, Tong N
2007-07-27  1:34               ` Tong Li
2007-07-27 17:16                 ` Chris Snook
2007-07-27 19:03                   ` Tong Li
2007-07-27 22:20                     ` Bill Huey
2007-07-27 23:36                     ` Chris Snook
2007-07-28  0:54                       ` Bill Huey
2007-07-28  2:59                         ` Chris Snook
2007-07-28 19:38                           ` Tong Li
2007-07-29  2:40                             ` Chris Snook
2007-07-28 19:23                       ` Tong Li
2007-07-29  3:01                         ` Chris Snook
2007-07-25 18:20     ` Li, Tong N
2007-07-25 19:18       ` 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=46A66A88.8070307@redhat.com \
    --to=csnook@redhat.com \
    --cc=cfriesen@nortel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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.