From: David Rientjes <rientjes@google.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Minchan Kim <minchan.kim@gmail.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [PATCH 5/9] oom: cleanup has_intersects_mems_allowed()
Date: Mon, 21 Jun 2010 13:09:51 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1006211305590.8367@chino.kir.corp.google.com> (raw)
In-Reply-To: <20100617134601.FBA7.A69D9226@jp.fujitsu.com>
On Mon, 21 Jun 2010, KOSAKI Motohiro wrote:
> > I disagree that the renaming of the variables is necessary, please simply
> > change the while (tsk != start) to use while_each_thread(tsk, start);
>
> This is common naming rule of while_each_thread(). please grep.
>
I disagree, there's no sense in substituting variable names like "tsk" for
`p' and removing a very clear and obvious "start" task: it doesn't improve
code readability.
I'm in favor of changing the while (tsk != start) to
while_each_thread(tsk, start) which is very trivial to understand and much
more readable than while_each_thread(p, tsk). With the latter, it's not
clear whether `p' or "tsk" is the iterator and which is the constant.
--
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:[~2010-06-21 20:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 1:45 [PATCH 1/9] oom: don't try to kill oom_unkillable child KOSAKI Motohiro
2010-06-17 1:51 ` [PATCH 2/9] oom: oom_kill_process() doesn't select kthread child KOSAKI Motohiro
2010-06-21 20:14 ` David Rientjes
2010-06-30 9:26 ` KOSAKI Motohiro
2010-06-17 1:51 ` [PATCH 3/9] oom: make oom_unkillable_task() helper function KOSAKI Motohiro
2010-06-21 20:15 ` David Rientjes
2010-06-30 9:26 ` KOSAKI Motohiro
2010-06-17 1:51 ` [PATCH 4/9] oom: oom_kill_process() need to check p is unkillable KOSAKI Motohiro
2010-06-17 4:19 ` David Rientjes
2010-06-21 11:45 ` KOSAKI Motohiro
2010-06-21 14:00 ` Minchan Kim
2010-06-21 20:04 ` David Rientjes
2010-06-30 9:26 ` KOSAKI Motohiro
2010-06-17 1:51 ` [PATCH 5/9] oom: cleanup has_intersects_mems_allowed() KOSAKI Motohiro
2010-06-17 4:20 ` David Rientjes
2010-06-21 11:45 ` KOSAKI Motohiro
2010-06-21 20:09 ` David Rientjes [this message]
2010-06-30 9:26 ` KOSAKI Motohiro
2010-06-17 1:51 ` [PATCH 6/9] oom: unify CAP_SYS_RAWIO check into other superuser check KOSAKI Motohiro
2010-06-17 4:18 ` David Rientjes
2010-06-21 11:46 ` KOSAKI Motohiro
2010-06-17 1:51 ` [PATCH 8/9] oom: give the dying task a higher priority KOSAKI Motohiro
2010-06-17 1:51 ` [PATCH 9/9] oom: multi threaded process coredump don't make deadlock KOSAKI Motohiro
2010-06-17 1:51 ` [PATCH 7/9] oom: remove child->mm check from oom_kill_process() KOSAKI Motohiro
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.1006211305590.8367@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.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=minchan.kim@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