Re: [RFC] cpuset relative memory policies - second choice

On Thu, 1 Nov 2007, Paul Jackson wrote:

> A library such as libnuma can set them, yes, but not everyone uses
> libnuma.  Basically everyone uses the standard C library, glibc, which
> has the system call wrappers, but these wrappers should not be setting
> optional flags.
> 

I think what would end up happening is that additional functions would be 
added to libnuma that would effect the system-wide nodemask numbering by 
simply OR'ing the MPOL_F_MODE_SYS_WIDE flag as part of the mode actual.

		David
-
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:
  • [RFC] cpuset relative memory policies - second choice
    • From: Paul Jackson <[email protected]>
  • Re: [RFC] cpuset relative memory policies - second choice
    • From: Christoph Lameter <[email protected]>
  • Re: [RFC] cpuset relative memory policies - second choice
    • From: Paul Jackson <[email protected]>
  • Re: [RFC] cpuset relative memory policies - second choice
    • From: Christoph Lameter <[email protected]>
  • Re: [RFC] cpuset relative memory policies - second choice
    • From: Paul Jackson <[email protected]>
  • Re: [RFC] cpuset relative memory policies - second choice
    • From: Christoph Lameter <[email protected]>
  • Re: [RFC] cpuset relative memory policies - second choice
    • From: Paul Jackson <[email protected]>
  • Re: [RFC] cpuset relative memory policies - second choice
    • From: Christoph Lameter <[email protected]>
  • Re: [RFC] cpuset relative memory policies - second choice
    • From: Paul Jackson <[email protected]>
  • Re: [RFC] cpuset relative memory policies - second choice
    • From: Christoph Lameter <[email protected]>
  • Re: [RFC] cpuset relative memory policies - second choice
    • From: Paul Jackson <[email protected]>

• Prev by Date: Re: [RFC] cpuset relative memory policies - second choice
• Next by Date: Re: [PATCH] x86: check boundary in count/setup_resource called by get_current_resources
• Previous by thread: Re: [RFC] cpuset relative memory policies - second choice
• Next by thread: Re: [RFC] cpuset relative memory policies - second choice
• 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]