[lkml]   [2008]   [Mar]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 0/2] Cpuset hardwall flag: Introduction
    On Wed, 5 Mar 2008 06:23:18 -0600 Paul Jackson <> wrote:

    > 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 make that special effort almost 100% of the time. The changelog for the
    first patch becomes:

    <text from [0/n]>

    This patch:

    <text from [1/n]>

     \ /
      Last update: 2008-03-05 19:13    [W:0.020 / U:11.328 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site