From: Paul Menage <menage@google.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"balbir@linux.vnet.ibm.com" <balbir@linux.vnet.ibm.com>
Subject: Re: [PATCH 2/2] cgroup: exlclude release rmdir
Date: Tue, 30 Jun 2009 17:27:02 -0700 [thread overview]
Message-ID: <6599ad830906301727wcb6b292uc3c46451f8844392@mail.gmail.com> (raw)
In-Reply-To: <20090701090959.4cbdb03e.kamezawa.hiroyu@jp.fujitsu.com>
On Tue, Jun 30, 2009 at 5:09 PM, KAMEZAWA
Hiroyuki<kamezawa.hiroyu@jp.fujitsu.com> wrote:
> On Wed, 1 Jul 2009 08:40:37 +0900
> Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp> wrote:
>
>> On Tue, 30 Jun 2009 09:18:03 -0700, Paul Menage <menage@google.com> wrote:
>> > On Tue, Jun 30, 2009 at 2:23 AM, KAMEZAWA
>> > Hiroyuki<kamezawa.hiroyu@jp.fujitsu.com> wrote:
>> > > This patch is _not_ tested by Nishimura.
>> >
>> > True, but it's functionally identical to, and simpler than, the one
>> > that was tested.
>> >
>> I agree.
>> I'll test with both of these patches folded.
>>
> Hm,ok. I'll post merged one today.
> But I don't like cosmeticized bugfix patch ;(
>
It only looks "cosmeticized" because of the evolution of your fix. The
first patch added a new function that exposed internal details of
cgroups, and the second patch removes the addition in favour of a
different new function that doesn't expose internal details as much; a
single patch that just adds the simpler new function is easier to
judge as intuitively correct (separately from Daisuke's testing) than
one that exposes more internal details.
Paul
next prev parent reply other threads:[~2009-07-01 0:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 9:01 [PATCH 0/2] memcg: fix cgroup rmdir hang v3 KAMEZAWA Hiroyuki
2009-06-30 9:02 ` [PATCH 1/2] " KAMEZAWA Hiroyuki
2009-06-30 9:03 ` [PATCH 2/2] cgroup: exlclude release rmdir KAMEZAWA Hiroyuki
2009-06-30 9:15 ` Paul Menage
2009-06-30 9:23 ` KAMEZAWA Hiroyuki
2009-06-30 16:18 ` Paul Menage
2009-06-30 23:40 ` Daisuke Nishimura
2009-07-01 0:09 ` KAMEZAWA Hiroyuki
2009-07-01 0:27 ` Paul Menage [this message]
2009-07-01 1:04 ` KAMEZAWA Hiroyuki
2009-07-01 18:17 ` Paul Menage
2009-07-02 1:27 ` Li Zefan
2009-07-01 1:47 ` [PATCH] memcg: fix cgroup rmdir hang v4 KAMEZAWA Hiroyuki
2009-07-01 15:57 ` Paul Menage
2009-07-01 23:35 ` Daisuke Nishimura
2009-07-02 6:30 ` Balbir Singh
2009-07-02 6:35 ` KAMEZAWA Hiroyuki
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=6599ad830906301727wcb6b292uc3c46451f8844392@mail.gmail.com \
--to=menage@google.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nishimura@mxp.nes.nec.co.jp \
/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
all inboxes | Powered by JetHome®