From: Jens Axboe <jaxboe@fusionio.com>
To: Jan Kara <jack@suse.cz>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2 v3] Small cleanup of bdi_forker_thread()
Date: Fri, 2 Sep 2011 17:16:46 -0600 [thread overview]
Message-ID: <4E6163DE.4030208@fusionio.com> (raw)
In-Reply-To: <20110902231212.GH12182@quack.suse.cz>
On 2011-09-02 17:12, Jan Kara wrote:
> On Fri 02-09-11 17:07:10, Jens Axboe wrote:
>> On 2011-09-02 16:54, Jan Kara wrote:
>>>
>>> Hi Jens,
>>>
>>> so after I realized how I underestimated subtlety of bdi_forker_thread()
>>> here are two small cleanups to it. The first one puts clearing of BDI_pending
>>> in a more natural place, the second patch adds a comment so that fools like
>>> me don't try to optimize the function in a wrong place...
>>
>> Thanks Jan, I've queued it up for 3.1. I've marked it as stable, looks
>> like we need it from 2.6.36 and above.
> Thanks. But is it really a stable material? It's just a cleanup after
> all...
I guess it's not strictly stable material, since it's not fixing a
problematic issue.
--
Jens Axboe
prev parent reply other threads:[~2011-09-02 23:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 22:54 [PATCH 0/2 v3] Small cleanup of bdi_forker_thread() Jan Kara
2011-09-02 22:54 ` [PATCH 1/2] mm: Cleanup clearing of BDI_pending bit in bdi_forker_thread() Jan Kara
2011-09-04 3:04 ` Wu Fengguang
2011-09-04 4:13 ` Wu Fengguang
2011-09-05 10:06 ` Jan Kara
2011-09-05 12:50 ` Wu Fengguang
2011-09-02 22:54 ` [PATCH 2/2] mm: Add comment explaining task state setting " Jan Kara
2011-09-04 3:05 ` Wu Fengguang
2011-09-05 10:01 ` Jan Kara
2011-09-05 12:44 ` Wu Fengguang
2011-09-05 15:53 ` Jan Kara
2011-09-07 22:19 ` Andrew Morton
2011-09-08 0:29 ` Wu Fengguang
2011-09-02 23:07 ` [PATCH 0/2 v3] Small cleanup of bdi_forker_thread() Jens Axboe
2011-09-02 23:12 ` Jan Kara
2011-09-02 23:16 ` Jens Axboe [this message]
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=4E6163DE.4030208@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.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.