From: Minchan Kim <minchan.kim@gmail.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
chris.mason@oracle.com, hch@infradead.org, tytso@mit.edu,
akpm@linux-foundation.org, jack@suse.cz,
trond.myklebust@fys.uio.no
Subject: Re: [PATCH 4/7] writeback: use RCU to protect bdi_list
Date: Mon, 14 Sep 2009 20:10:02 +0900 [thread overview]
Message-ID: <20090914201002.0ca94166.minchan.kim@barrios-desktop> (raw)
In-Reply-To: <1252920994-11141-5-git-send-email-jens.axboe@oracle.com>
On Mon, 14 Sep 2009 11:36:31 +0200
Jens Axboe <jens.axboe@oracle.com> wrote:
> Now that bdi_writeback_all() no longer handles integrity writeback,
> it doesn't have to block anymore. This means that we can switch
> bdi_list reader side protection to RCU.
>
> Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
> ---
> fs/fs-writeback.c | 4 +-
> include/linux/backing-dev.h | 1 +
> mm/backing-dev.c | 76 +++++++++++++++++++++++++++++++------------
> mm/page-writeback.c | 8 ++--
> 4 files changed, 62 insertions(+), 27 deletions(-)
>
> diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c
> index 5d4bd1c..d7592c7 100644
> --- a/fs/fs-writeback.c
> +++ b/fs/fs-writeback.c
> @@ -849,7 +849,7 @@ static void bdi_writeback_all(struct writeback_control *wbc)
>
> WARN_ON(wbc->sync_mode == WB_SYNC_ALL);
>
> - spin_lock(&bdi_lock);
> + rcu_read_lock();
>
> list_for_each_entry(bdi, &bdi_list, bdi_list) {
list_for_each_entry_rcu?
--
Kind regards,
Minchan Kim
next prev parent reply other threads:[~2009-09-14 11:10 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 9:36 [PATCH 0/7] Post merge per-bdi writeback patches v2 Jens Axboe
2009-09-14 9:36 ` [PATCH 1/7] writeback: merely wakeup flusher thread if work allocation fails for WB_SYNC_NONE Jens Axboe
2009-09-14 12:34 ` Jan Kara
2009-09-14 12:39 ` Jens Axboe
2009-09-14 13:19 ` Christoph Hellwig
2009-09-14 9:36 ` [PATCH 2/7] Assign bdi in super_block Jens Axboe
2009-09-14 13:02 ` Jan Kara
2009-09-14 18:25 ` Trond Myklebust
2009-09-14 18:36 ` Jens Axboe
2009-09-15 10:14 ` Jan Kara
2009-09-15 10:22 ` Jens Axboe
2009-09-15 13:16 ` Trond Myklebust
2009-09-14 9:36 ` [PATCH 3/7] writeback: only use bdi_writeback_all() for WB_SYNC_NONE writeout Jens Axboe
2009-09-14 13:12 ` Jan Kara
2009-09-14 9:36 ` [PATCH 4/7] writeback: use RCU to protect bdi_list Jens Axboe
2009-09-14 11:10 ` Minchan Kim [this message]
2009-09-14 11:11 ` Jens Axboe
2009-09-14 9:36 ` [PATCH 5/7] writeback: inline allocation failure handling in bdi_alloc_queue_work() Jens Axboe
2009-09-14 13:13 ` Jan Kara
2009-09-14 9:36 ` [PATCH 6/7] writeback: separate starting of sync vs opportunistic writeback Jens Axboe
2009-09-14 13:33 ` Jan Kara
2009-09-14 13:42 ` Christoph Hellwig
2009-09-14 19:28 ` Jens Axboe
2009-09-14 19:42 ` Jens Axboe
2009-09-15 9:08 ` Jan Kara
2009-09-15 9:14 ` Jens Axboe
2009-09-15 11:44 ` Jens Axboe
2009-09-15 12:58 ` Jan Kara
2009-09-15 13:04 ` Jens Axboe
2009-09-15 13:08 ` Christoph Hellwig
2009-09-15 13:17 ` Jens Axboe
2009-09-15 14:01 ` Jan Kara
2009-09-15 14:09 ` Chris Mason
2009-09-14 9:36 ` [PATCH 7/7] writeback: splice dirty inode entries to default bdi on bdi_destroy() Jens Axboe
2009-09-14 10:56 ` Jens Axboe
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=20090914201002.0ca94166.minchan.kim@barrios-desktop \
--to=minchan.kim@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=jens.axboe@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
--cc=tytso@mit.edu \
/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.