All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Christoph Hellwig <hch@caldera.de>
Cc: Thomas Widmann <thomas.widmann@icn.siemens.de>,
	linux-kernel@vger.kernel.org
Subject: Re: SMP: bind process to cpu
Date: Sat, 17 Feb 2001 15:13:45 +0100	[thread overview]
Message-ID: <3A8E8719.DD58EB7C@colorfullife.com> (raw)
In-Reply-To: <200102171327.OAA00342@ns.caldera.de>

Christoph Hellwig wrote:
> 
> In article <BGEDIODHBENLENEMBEPAEEDFCAAA.thomas.widmann@icn.siemens.de> you wrote:
> > Hi,
> >
> > I run an 3*XEON 550MHz Primergy with 2GB of RAM.
> > On this machine, i have compiled kernel 2.4.0SMP.
> >
> > Is it possible to bind a process to a specific
> > cpu on this SMP machine (process affinity) ?
> 
> Linux 2.4 is mostlu ready for process affinity, but it is not (yet)
> exported to userspace.  I've attached at patch by Nick Pollitt from SGI
> that allows to enable process pinning using prctl().
> 
> > I there something like pset ?
> 
> I've seen patches for SGI-like psets for 2.2.<something>, but not for 2.4.
>
>         Christoph
>
You must also update wake_process_synchroneous(), otherwise you can get
lost wakeups with pipes.

Something like

>         if (!(p->cpus_allowed & (1 << smp_processor_id()))
>                 reschedule_idle(p);

must be added after add_to_runqueue().

Ingo Molnar did some testing with tux2, and under high load wakeups were
lost without such a patch.

--
	Manfred

  reply	other threads:[~2001-02-17 14:13 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 [this message]
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
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=3A8E8719.DD58EB7C@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=hch@caldera.de \
    --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 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.