From: Coywolf Qi Hunt <coywolf@gmail.com>
To: Paul Jackson <pj@sgi.com>
Cc: Andrew Morton <akpm@osdl.org>, Mel Gorman <mel@csn.ul.ie>,
linux-kernel@vger.kernel.org,
Dinakar Guniguntala <dino@in.ibm.com>,
Joel Schopp <jschopp@austin.ibm.com>,
Simon Derr <Simon.Derr@bull.net>,
Linus Torvalds <torvalds@osdl.org>,
Dave Hansen <haveblue@us.ibm.com>
Subject: Re: [PATCH 1/4] cpusets oom_kill tweaks
Date: Thu, 1 Sep 2005 17:39:39 +0800 [thread overview]
Message-ID: <2cd57c900509010239670c07a2@mail.gmail.com> (raw)
In-Reply-To: <20050901090859.18441.67380.sendpatchset@jackhammer.engr.sgi.com>
On 9/1/05, Paul Jackson <pj@sgi.com> wrote:
> This patch applies a few comment and code cleanups to mm/oom_kill.c
> prior to applying a few small patches to improve cpuset management of
> memory placement.
>
> The comment changed in oom_kill.c was seriously misleading. The code
> layout change in select_bad_process() makes room for adding another
> condition on which a process can be spared the oom killer (see the
> subsequent cpuset_nodes_overlap patch for this addition).
>
> Also a couple typos and spellos that bugged me, while I was here.
>
> This patch should have no material affect.
Why bother to have just added a variable, `releasing'?
--
Coywolf Qi Hunt
http://sosdg.org/~coywolf/
next prev parent reply other threads:[~2005-09-01 9:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 9:08 [PATCH 0/4] cpusets mems_allowed constrain GFP_KERNEL, oom killer Paul Jackson
2005-09-01 9:08 ` [PATCH 1/4] cpusets oom_kill tweaks Paul Jackson
2005-09-01 9:39 ` Coywolf Qi Hunt [this message]
2005-09-01 9:58 ` Paul Jackson
2005-09-01 10:49 ` Coywolf Qi Hunt
2005-09-01 9:09 ` [PATCH 2/4] cpusets new __GFP_HARDWALL flag Paul Jackson
2005-09-01 9:09 ` [PATCH 3/4] cpusets formalize intermediate GFP_KERNEL containment Paul Jackson
2005-09-01 9:09 ` [PATCH 4/4] cpusets confine oom_killer to mem_exclusive cpuset Paul Jackson
2005-09-06 8:08 ` [PATCH 0/4] cpusets mems_allowed constrain GFP_KERNEL, oom killer Paul Jackson
2005-09-06 22:29 ` Paul Jackson
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=2cd57c900509010239670c07a2@mail.gmail.com \
--to=coywolf@gmail.com \
--cc=Simon.Derr@bull.net \
--cc=akpm@osdl.org \
--cc=dino@in.ibm.com \
--cc=haveblue@us.ibm.com \
--cc=jschopp@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=pj@sgi.com \
--cc=torvalds@osdl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.