Messages in this thread | | | Date | Wed, 5 Mar 2008 06:23:18 -0600 | From | Paul Jackson <> | Subject | Re: [PATCH 0/2] Cpuset hardwall flag: Introduction |
| |
Paul M wrote: > Currently the cpusets mem_exclusive flag is overloaded to mean both > "no-overlapping" and "no GFP_KERNEL allocations outside this cpuset". > > These patches add a new mem_hardwall flag with just the allocation > restriction part of the mem_exclusive semantics, without breaking > backwards-compatibility for those who continue to use just > mem_exclusive.
... too bad this nice comment wasn't included in PATCH 2/2, so that it would automatically make it into the record of history - the source control log message (as best I understand how Andrew's tools work, comments off in their own, codeless patch "PATCH 0/N" don't make it to the source control log, except when Andrew chooses to make a special effort.)
-- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson <pj@sgi.com> 1.940.382.4214
| |