From: Nathan Lynch <ntl@pobox.com>
To: "Dr. David Alan Gilbert" <linux@treblig.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hotplug CPU and setaffinity?
Date: Sat, 23 Apr 2005 13:22:27 -0500 [thread overview]
Message-ID: <20050423182227.GE18688@otto> (raw)
In-Reply-To: <20050423173514.GA7111@gallifrey>
Dr. David Alan Gilbert wrote:
>
> I got to wondering how Hotplug CPU and sched_setaffinity interact;
> if I have a process that has its affinity set to one CPU and some
> nasty person comes along and unplugs it what happens to that process-
> does it get scheduled onto another cpu, just not get any time or
> die ?
The affinity of the process is reset to the default and it is migrated
to another cpu, for better or worse. The kernel assumes the admin
know what he/she is doing.
>
> In particular I was thinking of the cases where a thread has a
> functional reason for remaining on one particular CPU (e.g. if you
> had calibrated for some feature of that CPU say its time stamp
> counter skew/speed). Another case would be a set of threads which
> had set their affinity to the same CPU and then made memory
> consistency or locking assumptions that wouldn't be valid
> if they got rescheduled onto different CPUs.
Yeah. But I don't think this is an issue to be solved in the kernel.
Applications that are this sensitive to cpu hotplugging need to
arrange to be notified before the hotplug occurs, which I think would
be best done with dbus or some other IPC.
Nathan
next prev parent reply other threads:[~2005-04-23 18:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-23 17:35 Hotplug CPU and setaffinity? Dr. David Alan Gilbert
2005-04-23 18:22 ` Nathan Lynch [this message]
2005-04-24 12:35 ` Dr. David Alan Gilbert
2005-04-25 16:00 ` Joel Schopp
2005-04-25 17:28 ` Dave Gilbert (Home)
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=20050423182227.GE18688@otto \
--to=ntl@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.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 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.