public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Gerrit Huizenga <gh@us.ibm.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Lse-tech] CPUSET Proposal
Date: Wed, 24 Sep 2003 19:32:29 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106443206906619@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106442121824485@msgid-missing>

This might be worth comparing notes on with the CKRM folks (cc:'d above).

gerrit

On Wed, 24 Sep 2003 17:59:01 +0200, Simon Derr wrote:
> 
> Hi,
> 
> We have developped a new feature in the Linux kernel, controlling CPU
> placements, which are useful on large SMP machines, especially NUMA ones.
> We call it CPUSETS, and we would highly appreciate to know about anyone
> who would be interested in such a feature. This has been somewhat inspired
> by the pset or cpumemset patches existing for Linux 2.4.
> 
> CPUSETs are lightweight objects in the linux kernel that enable users to
> partition their multiprocessor machine by creating execution areas. A
> virtualization layer has been added so it becomes possible to split a
> machine in terms of CPUs.
> 
> Furthermore, HPC applications often need to bind their processes to a
> specific CPU, and can achieve this by calling sched_setaffinity() in the
> recent Linux kernels. But running several HPC applications on a large
> system will result in several processes running on the same processor.
> This problem is addressed by the CPUSET mechanism.
> 
> 
> CPUSETS allow to:
> ----------------
> 1/ create sets of CPUs on the system, and bind applications to them
> 
> 2/ translate the masks of CPUs given to sched_setaffinity() so they stay
>    inside the set of CPUs. With this mechanism, processors are virtualized,
>    for the use of sched_setaffinity() and /proc information. Thus, any former
>    application using this syscall to bind processes to processors will
>    work with virtual CPUs without any change.
> 
> 3/ provide a way to create sets of cpus *inside* a set of cpus : hence a
>    system administrator can partition a system among users, and users can
>    partition their partition among their applications.
> 
> 4/ Change on the fly the execution area of a whole set of processes (to
>    give more resources to a critical application, for example).
> 
> ...
> 5/ In the future, probably associate a memory allocation policy (such as
> local node, or round robin) to a set of cpus.
> 
> 
> These features have been implemented as a kernel patch for Linux 2.6 and a
> suite of userland tools.
> 
> You can find the associated manpages and a slightly more detailed
> explanation here: http://www.bullopensource.org/cpuset/
> 
> Any feedback, comment or opinion is welcome:
> 	Simon.Derr@Bull.net,
> 	Sylvain.Jaugey@bull.net
> 
> Thanks,
> 
> 	Simon and Sylvain.

  parent reply	other threads:[~2003-09-24 19:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-24 16:30 [Lse-tech] CPUSET Proposal Stephen Hemminger
2003-09-24 17:02 ` David Mosberger
2003-09-24 19:32 ` Gerrit Huizenga [this message]
2003-09-24 21:42 ` Paul Jackson
2003-09-25  5:40 ` Paul Jackson
2003-09-25  5:44 ` Paul Jackson
2003-09-25  6:02 ` William Lee Irwin III
2003-09-25  6:57 ` David Mosberger
2003-09-25  7:07 ` David Mosberger
2003-09-25  7:08 ` William Lee Irwin III
2003-09-25  7:14 ` William Lee Irwin III
2003-09-25  9:04 ` Dave Hansen
2003-09-25 18:07 ` Shailabh Nagar
2003-09-25 18:08 ` William Lee Irwin III
2003-09-25 20:50 ` Shailabh Nagar
2003-09-26  7:36 ` Simon Derr
2003-09-26  9:58 ` Paul Jackson

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=marc-linux-ia64-106443206906619@msgid-missing \
    --to=gh@us.ibm.com \
    --cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox