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

David wrote:
> The nodemask passed to set_mempolicy() will always have exactly one
> meaning: the system nodes that the policy is intended for.

Ok - that makes the meaning of Choice C clearer to me.  Thank-you.

We've already got two Choices, one released and one in the oven.  Is
there an actual, real world situation, motivating this third Choice?

-- 
                  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: [patch 2/2] cpusets: add interleave_over_allowed option
    • From: David Rientjes <[email protected]>

• 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]>
  • 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: Paul Jackson <[email protected]>
  • Re: [patch 2/2] cpusets: add interleave_over_allowed option
    • From: Christoph Lameter <[email protected]>
  • Re: [patch 2/2] cpusets: add interleave_over_allowed option
    • From: Paul Jackson <[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: Paul Jackson <[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: Paul Jackson <[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: Paul Jackson <[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: Paul Jackson <[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: Paul Jackson <[email protected]>
  • Re: [patch 2/2] cpusets: add interleave_over_allowed option
    • From: David Rientjes <[email protected]>

• Prev by Date: Re: [PATCH] mmap: restore -ENODEV on missing f_op->mmap
• Next by Date: Re: [patch 2/2] cpusets: add interleave_over_allowed option
• 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]