public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Dobson <colpatch@us.ibm.com>
To: dino@in.ibm.com
Cc: Andrew Morton <akpm@osdl.org>, Paul Jackson <pj@sgi.com>,
	Simon Derr <Simon.Derr@bull.net>,
	Dipankar Sarma <dipankar@in.ibm.com>,
	lkml <linux-kernel@vger.kernel.org>,
	lse-tech <lse-tech@lists.sourceforge.net>,
	Ingo Molnar <mingo@elte.hu>, Jesse Barnes <jbarnes@sgi.com>
Subject: Re: [PATCH 1/3] Dynamic sched domains: sched changes
Date: Thu, 19 May 2005 13:09:27 -0700	[thread overview]
Message-ID: <428CF277.4070500@us.ibm.com> (raw)
In-Reply-To: <20050519150435.GA6073@in.ibm.com>

Dinakar Guniguntala wrote:
> Hello Andrew,
> 
> The following patches add dynamic sched domains functionality that was
> extensively discussed on lkml and lse-tech.
> I would like to see this added to -mm
> 
> o The main advantage with this feature is that it ensures that the scheduler
>   load balacing code only balances against the cpus that are in the sched
>   domain as defined by an exclusive cpuset and not all of the cpus in the
>   system. This removes any overhead due to load balancing code trying to
>   pull tasks outside of the cpu exclusive cpuset only to be prevented by
>   the tasks' cpus_allowed mask.
> o cpu exclusive cpusets are useful for servers running orthogonal
>   workloads such as RT applications requiring low latency and HPC
>   applications that are throughput sensitive
> 
> o It provides a new API partition_sched_domains in sched.c
>   that makes dynamic sched domains possible.
> o cpu_exclusive cpusets sets are now associated with a sched domain.
>   Which means that the users can dynamically modify the sched domains
>   through the cpuset file system interface
> o ia64 sched domain code has been updated to support this feature as well
> o Currently, this does not support hotplug. (However some of my tests
>   indicate hotplug+preempt is currently broken)
> o I have tested it extensively on x86.
> o This should have very minimal impact on performance as none of
>   the fast paths are affected
> 
>         -Dinakar
> 
> Signed-off-by: Dinakar Guniguntala <dino@in.ibm.com>
> Acked-by: Paul Jackson <pj@sgi.com>
> Acked-by: Nick Piggin <nickpiggin@yahoo.com.au>
> 
>  linux-2.6.12-rc4-mm1-1/include/linux/sched.h     |    2
>  linux-2.6.12-rc4-mm1-1/kernel/sched.c            |  130 +++++++++++++++--------
>  linux-2.6.12-rc4-mm1-2/Documentation/cpusets.txt |   16 ++
>  linux-2.6.12-rc4-mm1-2/kernel/cpuset.c           |   89 +++++++++++++--
>  linux-2.6.12-rc4-mm1-3/arch/ia64/kernel/domain.c |   76 +++++++------
>  5 files changed, 225 insertions(+), 88 deletions(-)

Looks good to me, Dinakar!

Acked-by: Matthew Dobson <colpatch@us.ibm.com>

-Matt

      parent reply	other threads:[~2005-05-19 20:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19 15:04 [PATCH 1/3] Dynamic sched domains: sched changes Dinakar Guniguntala
2005-05-19 15:06 ` [PATCH 2/3] Dynamic sched domains: cpuset changes Dinakar Guniguntala
2005-05-19 15:07 ` [PATCH 3/3] Dynamic sched domains: ia64 changes Dinakar Guniguntala
2005-05-19 20:09 ` Matthew Dobson [this message]

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=428CF277.4070500@us.ibm.com \
    --to=colpatch@us.ibm.com \
    --cc=Simon.Derr@bull.net \
    --cc=akpm@osdl.org \
    --cc=dino@in.ibm.com \
    --cc=dipankar@in.ibm.com \
    --cc=jbarnes@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=mingo@elte.hu \
    --cc=pj@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox