Re: [RFC] cpuset: add interface to isolated cpus

Nick wrote:
> This should be done outside cpusets.

So ... where should it be done?

And what would be better about that other place?

And by the way, I see in another patch you put some other
stuff for configuring sched domains in the root cpuset.
If the root cpuset was the right place for that, why isn't
it the right place for this? ... strange.

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

---

• Follow-Ups:
  • Re: [RFC] cpuset: add interface to isolated cpus
    • From: Nick Piggin <[email protected]>

• References:
  • [RFC] cpuset: add interface to isolated cpus
    • From: Paul Jackson <[email protected]>
  • Re: [RFC] cpuset: add interface to isolated cpus
    • From: Nick Piggin <[email protected]>

• Prev by Date: Re: [PATCH 1/1] Char: mxsers, correct tty driver name
• Next by Date: [PATCH 1/2] VFS: Make d_materialise_unique() enforce directory uniqueness
• Previous by thread: Re: [RFC] cpuset: add interface to isolated cpus
• Next by thread: Re: [RFC] cpuset: add interface to isolated cpus
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]