public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <andrewm@uow.edu.au>
To: Thomas Widmann <thomas.widmann@icn.siemens.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SMP: bind process to cpu
Date: Sun, 18 Feb 2001 12:01:36 +1100	[thread overview]
Message-ID: <3A8F1EF0.EC1CEEE5@uow.edu.au> (raw)
In-Reply-To: <3A8E8C8F.A2A9E69E@uow.edu.au> <BGEDIODHBENLENEMBEPAIEDFCAAA.thomas.widmann@icn.siemens.de>

Thomas Widmann wrote:
> ...
> * Andrew Morton wrote:
> 
> >       http://www.uow.edu.au/~andrewm/linux/#cpus_allowed
> >
> > You just write a bitmask into it.
> 
> Thanks for this information. I patched my the kernel with it.
> After rebooting with the new kernel i can see the bitmask
> for every process running on my server.
> 
> #cat /proc/1310/cpus_allowed
> ffffffff
> 
> Now, if i want to run this process on only one cpu, i which way
> do i have to set the bitmask ?
> Let's say, i want to run it on cpu0. how look's the bitmask ?

Each bit corresponds to a logical CPU on which the task
is permitted to run.  So 1->CPU0, 2->CPU1, 5->CPU0+CPU2, etc.

But it does seem there are problems with the scheduler
which occur when cpus_allowed it not all-ones.  I didn't
observe any problems in the 1-2 hours testing which I
needed that patch for, so it should be OK for experimentation
purposes..

-

  parent reply	other threads:[~2001-02-18  0:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-17 12:36 SMP: bind process to cpu Thomas Widmann
2001-02-17 13:27 ` Christoph Hellwig
2001-02-17 14:13   ` Manfred Spraul
2001-02-17 17:47     ` Christoph Hellwig
2001-02-17 14:37 ` Andrew Morton
2001-02-17 19:08   ` Thomas Widmann
2001-02-17 19:57     ` Francis Galiegue
2001-02-18  1:01     ` Andrew Morton [this message]
2001-02-17 19:49 ` Tim Hockin

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=3A8F1EF0.EC1CEEE5@uow.edu.au \
    --to=andrewm@uow.edu.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas.widmann@icn.siemens.de \
    /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