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

On Fri, 26 Oct 2007, Paul Jackson wrote:

> Christoph wrote:
> > Yes. We should default to Choice B. Add an option MPOL_MF_RELATIVE to 
> > enable that functionality? A new version of numactl can then enable
> > that by default for newer applications.
> 
> I'm confused.  If B is the default, then we don't need a flag to
> enable it, rather we need a flag to go back to the old choice A.

Dont we need it for numactl to preserve backward compatibility? numactl 
can set that flag by default for newer software. We likely need a new 
major release of numactl.
 
> Perhaps, either way, whatever compatibility flag we have should be
> something that can be forced on an application from the outside,
> perhaps as a per-system mode flag in /sys, or a per-cpuset mode flag,
> or a per-task operation, by what mechanism is not clear.

libnuma can take of that. But we need to have that flag for numactl to be 
backward compatible.

-
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: Paul Jackson <[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: Christoph Lameter <[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: 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: 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: 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: 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]>

• Prev by Date: Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
• Next by Date: Re: pci-disable-decode-of-io-memory-during-bar-sizing.patch
• 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]