public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Simon Derr <Simon.Derr@bull.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sched_setaffinity() and load balancing
Date: Wed, 18 Aug 2004 22:50:24 +1000	[thread overview]
Message-ID: <41235090.8090909@yahoo.com.au> (raw)
In-Reply-To: <Pine.A41.4.53.0408181338030.20680@isabelle.frec.bull.fr>

Simon Derr wrote:
> Hello,
> 
> This is probably a known issue, or even maybe the expected behaviour, but
> it seems that using sched_setaffinity() can severely disturb load
> balancing on recent kernels. My tests are with 2.6.8-rc3 but I suppose
> other kernel versions behave the same way.
> 

Yep, it shouldn't be anything new.

You could justify the problem by saying that by using setaffinity, the
user has asserted that they know best and so it is OK for the balancer
to crap itself.

Ideally it would be handled nicely, but not a lot of people care at the
moment.

      reply	other threads:[~2004-08-18 12:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-18 12:22 sched_setaffinity() and load balancing Simon Derr
2004-08-18 12:50 ` Nick Piggin [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=41235090.8090909@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=Simon.Derr@bull.net \
    --cc=linux-kernel@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