linux-kernel - Re: cpusets not cpu hotplug aware

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20060823120838.efbd79c2.pj@sgi.com>
Date:	Wed, 23 Aug 2006 12:08:38 -0700
From:	Paul Jackson <pj@....com>
To:	Anton Blanchard <anton@...ba.org>
Cc:	akpm@...l.org, simon.derr@...l.net, nathanl@...tin.ibm.com,
	linux-kernel@...r.kernel.org
Subject: Re: cpusets not cpu hotplug aware

Anton wrote:
> We have a userspace visible change to the sched
> affinity API when the cpusets option is enabled.

Yup - on cpuset kernels, sched_setaffinity is constrained to CPUs in a
tasks cpuset.  Also mbind and set_mempolicy are constrained to nodes in
the tasks cpuset.

This is a long standing, intentional part of the cpuset design.

Using udev isn't papering over it.  It's reflecting the reasonable
preference and expectation on systems using hotplug/unplug that
the default cpuset dynamically reflect the current online maps,
not the static maps as they were at boot.  And using udev is using
just the sort of mechanism one might expect to be used to adjust
the system when devices go on or off line.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@....com> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/