On Thu, 2005-03-10 at 12:11 -0800, Paul Jackson wrote: > Dave wrote: > > Perhaps default policies inherited from a cpuset, but overridden by > > other APIs would be a good compromise. > > Perhaps. The madvise() and numa calls (mbind, set_mempolicy) only > affect the current task, as is usually appropriate for calls that allow > specification of specific address ranges (strangers shouldn't be messing > in my address space). Some external means to set default policy for > whole tasks seems to be needed, as well, which could well be via the > cpuset.
Shouldn't a particular task know what the policy should be when it is launched? If the policy is only per-task and known at task exec time, I'd imagine that a simple exec wrapper setting a flag would be much more effective than even defining the policy in a cpuset. -- Dave - 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/
