On 10/24/2012 03:41 PM, Osier Yang wrote:
> On 2012年10月24日 21:36, Martin Kletzander wrote:
>> On 10/24/2012 03:29 PM, Osier Yang wrote:
>>> On 2012年10月24日 21:17, Martin Kletzander wrote:
On 10/24/2012 12:00 PM, Osier Yang wrote:
> When the cpu placement model is "auto", it sets the affinit
On 2012年10月24日 21:36, Martin Kletzander wrote:
On 10/24/2012 03:29 PM, Osier Yang wrote:
On 2012年10月24日 21:17, Martin Kletzander wrote:
On 10/24/2012 12:00 PM, Osier Yang wrote:
When the cpu placement model is "auto", it sets the affinity for
domain process with the advisory nodeset from numad
On 10/24/2012 03:29 PM, Osier Yang wrote:
> On 2012年10月24日 21:17, Martin Kletzander wrote:
>> On 10/24/2012 12:00 PM, Osier Yang wrote:
>>> When the cpu placement model is "auto", it sets the affinity for
>>> domain process with the advisory nodeset from numad, however,
>>> creating cgroup for the
On 2012年10月24日 21:17, Martin Kletzander wrote:
On 10/24/2012 12:00 PM, Osier Yang wrote:
When the cpu placement model is "auto", it sets the affinity for
domain process with the advisory nodeset from numad, however,
creating cgroup for the domain process (called emulator thread
in some contexts)
On 10/24/2012 12:00 PM, Osier Yang wrote:
> When the cpu placement model is "auto", it sets the affinity for
> domain process with the advisory nodeset from numad, however,
> creating cgroup for the domain process (called emulator thread
> in some contexts) later overrides that with pinning it to a
When the cpu placement model is "auto", it sets the affinity for
domain process with the advisory nodeset from numad, however,
creating cgroup for the domain process (called emulator thread
in some contexts) later overrides that with pinning it to all
available pCPUs.
How to reproduce:
* Config
