LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Paul Jackson <pj@sgi.com>
Cc: menage@google.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 0/2] Cpuset hardwall flag:  Introduction
Date: Wed, 5 Mar 2008 10:10:15 -0800	[thread overview]
Message-ID: <20080305101015.cdff44f2.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080305062318.3c7538c3.pj@sgi.com>

On Wed, 5 Mar 2008 06:23:18 -0600 Paul Jackson <pj@sgi.com> 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]>

      reply	other threads:[~2008-03-05 18:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05  7:52 [PATCH 0/2] Cpuset hardwall flag: Introduction menage
2008-03-05  7:52 ` [PATCH 1/2] Cpuset hardwall flag: Switch cpusets to use the bulk cgroup_add_files() API menage
2008-03-05  8:43   ` Li Zefan
2008-03-05 12:07   ` Paul Jackson
2008-03-05  7:52 ` [PATCH 2/2] Cpuset hardwall flag: Add a mem_hardwall flag to cpusets menage
2008-03-05 12:17   ` Paul Jackson
2008-03-05 12:23 ` [PATCH 0/2] Cpuset hardwall flag: Introduction Paul Jackson
2008-03-05 18:10   ` Andrew Morton [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080305101015.cdff44f2.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=menage@google.com \
    --cc=pj@sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).