Re: [patch 2/2] cpusets: add interleave_over_allowed option

> 
> Another thing occurs to me:  perhaps numactl would need an additional
> 'nodes' specifier such as 'allowed'.  Alternatively, 'all' could be
> redefined to me 'all allowed'.  This is independent of how you specify
> 'all allowed' to the system call.

cpuset support in libnuma/numactl is still incomplete. I'm also
not sure what the best way to handle this is.

Probably there should be a switch for both.

-Andi
-
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/

---

• References:
  • [patch 1/2] cpusets: extract mmarray loading from update_nodemask
    • From: David Rientjes <[email protected]>
  • Re: [patch 2/2] cpusets: add interleave_over_allowed option
    • From: David Rientjes <[email protected]>
  • Re: [patch 2/2] cpusets: add interleave_over_allowed option
    • From: Lee Schermerhorn <[email protected]>

• Prev by Date: Re: [patch 2/2] cpusets: add interleave_over_allowed option
• Next by Date: Re: last git: BUG: unable to handle kernel paging request at virtual address 92184900
• Previous by thread: Re: [patch 2/2] cpusets: add interleave_over_allowed option
• Next by thread: Re: [patch 2/2] cpusets: add interleave_over_allowed option
• 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]