From: David Rientjes <rientjes@google.com>
To: Thiago Farina <tfransosi@gmail.com>
Cc: Michal Hocko <mhocko@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Anton Vorontsov <anton.vorontsov@linaro.org>,
Oleg Nesterov <oleg@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [patch 2/2] mm, oom: fix race when specifying a thread as the oom origin
Date: Mon, 12 Nov 2012 14:28:17 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.00.1211121427580.29870@chino.kir.corp.google.com> (raw)
In-Reply-To: <CACnwZYcUEmEStT7uwN3O3=m34uLi9YnJSYWFPZafuzCy_t4uaw@mail.gmail.com>
On Mon, 12 Nov 2012, Thiago Farina wrote:
> > I didn't like the previous playing with the oom_score_adj and what you
> > propose looks much nicer.
> > Maybe s/oom_task_origin/task_oom_origin/ would be a better fit
> May be s/oom_task_origin/is_task_origin_oom? Just my 2 cents.
>
I like to prefix oom killer functions in the global namespace with "oom_"
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-11-12 22:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 9:26 [patch 1/2] mm, oom: change type of oom_score_adj to short David Rientjes
2012-11-08 9:27 ` [patch 2/2] mm, oom: fix race when specifying a thread as the oom origin David Rientjes
2012-11-08 15:51 ` Michal Hocko
2012-11-12 22:14 ` Thiago Farina
2012-11-12 22:28 ` David Rientjes [this message]
2012-11-08 15:35 ` [patch 1/2] mm, oom: change type of oom_score_adj to short Michal Hocko
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=alpine.DEB.2.00.1211121427580.29870@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=anton.vorontsov@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=oleg@redhat.com \
--cc=tfransosi@gmail.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