From: Nick Piggin <nickpiggin@yahoo.com.au>
To: YAMAMOTO Takashi <yamamoto@valinux.co.jp>
Cc: a.p.zijlstra@chello.nl, kamezawa.hiroyu@jp.fujitsu.com,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fix task dirty balancing
Date: Thu, 10 Jul 2008 17:23:36 +1000 [thread overview]
Message-ID: <200807101723.36713.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <20080710031051.887CA5A29@siro.lan>
On Thursday 10 July 2008 13:10, YAMAMOTO Takashi wrote:
> hi,
>
> thanks for the review.
>
> > On Wednesday 09 July 2008 09:38, YAMAMOTO Takashi wrote:
> > > hi,
> > >
> > > > Please beat me to cleaning up this stuff - otherwise I'll have to
> > > > look at it when I get back from holidays.
> > >
> > > how about the following?
> >
> > Quite good, however I would like to keep the buffers warning if it isn't
> > too difficult (it has already caught one or two real bugs).
>
> isn't the WARN_ON_ONCE in __set_page_dirty_nobuffers enough?
No, because it will skip warning if the page has buffers (which is a
very common case for fs/buffer.c :)).
> > Also, we should
> > split out the bugfix from the cleanup. But yes overall I think the result
> > looks quite nice.
>
> honestly, i don't think it makes much sense to separate the fix and
> the cleanup in this particular case. trying to keep the bug while
> the code cleanup naturally fixes it, or vice versa, would be a waste
> of time.
It always makes sense to separate fix and cleanup IMO. The most important
reason is that it makes it clearer to review the fix. Secondarily, it
makes it easier to ensure no unwanted changes in the cleanup part.
next prev parent reply other threads:[~2008-07-10 7:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 8:26 [PATCH] fix task dirty balancing YAMAMOTO Takashi
2008-07-02 20:27 ` Peter Zijlstra
2008-07-03 7:33 ` YAMAMOTO Takashi
2008-07-05 6:04 ` KAMEZAWA Hiroyuki
2008-07-05 9:30 ` Peter Zijlstra
2008-07-07 6:46 ` YAMAMOTO Takashi
2008-07-07 10:36 ` Nick Piggin
2008-07-08 23:38 ` YAMAMOTO Takashi
2008-07-09 7:41 ` Nick Piggin
2008-07-10 3:10 ` YAMAMOTO Takashi
2008-07-10 7:23 ` Nick Piggin [this message]
2008-07-24 0:27 ` YAMAMOTO Takashi
2008-07-24 15:08 ` Nick Piggin
2008-07-25 8:04 ` YAMAMOTO Takashi
2008-07-25 9:57 ` Peter Zijlstra
2008-07-28 5:50 ` YAMAMOTO Takashi
2008-07-28 7:24 ` Peter Zijlstra
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=200807101723.36713.nickpiggin@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yamamoto@valinux.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 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.