On Wednesday 01 March 2006 19:27, Paul Jackson wrote:
> > > 1) Are you content to have such a interleave of these particular file
> > > i/o slabs triggered by a mm/mempolicy.c option? Or do you think
> > > we need some sort of task external API to invoke this policy?
> >
> > Task external. mempolicy.c has no good way to handle multiple policies
> > like this. I was thinking of a simple sysctl
>
> No need to implement a sysctl for this. The current cpuset facility
> should provide just what you want, if I am understanding correctly.
The main reason i'm reluctant to use this is that the cpuset fast path
overhead (e.g. in memory allocators etc.) is quite large and I wouldn't like
to recommend people to enable all this overhead by default just to get
more useful dcache/inode behaviour on small NUMA systems.
-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/
[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]
