From: Jens Axboe <jens.axboe@oracle.com>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Cc: chris.mason@oracle.com, hch@infradead.org, tytso@mit.edu,
akpm@linux-foundation.org, jack@suse.cz,
trond.myklebust@fys.uio.no
Subject: [PATCH 0/4] Post merge per-bdi writeback patches
Date: Fri, 11 Sep 2009 13:50:28 +0200 [thread overview]
Message-ID: <1252669832-13553-1-git-send-email-jens.axboe@oracle.com> (raw)
Hi,
This is what I currently have queued up for post merge of the
writeback patchset. It contains:
- The bdi work allocation and queue cleanup from Christoph.
- An sb->s_bdi pointer that gets assigned in get_sb_bdev(), OR
from the fs ->fill_super() if the file system doesn't use
get_sb_bdev(). It is required for WB_SYNC_ALL writeback. Someone
more familiar with this code should check that it is done in the
right place. As usual, I'm unsure of NFS...
- Once the ->s_bdi is in place, we can get rid of bdi_writeback_all()
for WB_SYNC_ALL. WB_SYNC_ALL now has to use bdi_start_writeback().
This cleans up bdi_writeback_all() nicely.
- With bdi_writeback_all() only doing WB_SYNC_NONE, we can drop
the bdi_lock requirement and move to RCU for bdi_list.
Please take a good look and review/comment, thanks! This patchset
is based on top of writeback-v20. It boots and works fine for me.
fs/btrfs/disk-io.c | 1
fs/fs-writeback.c | 111 ++++++++----------------------------
fs/fuse/inode.c | 2
fs/super.c | 6 +
fs/sync.c | 9 ++
fs/ubifs/super.c | 1
include/linux/backing-dev.h | 1
include/linux/fs.h | 1
mm/backing-dev.c | 76 +++++++++++++++++-------
mm/page-writeback.c | 8 +-
10 files changed, 105 insertions(+), 111 deletions(-)
--
Jens Axboe
next reply other threads:[~2009-09-11 11:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 11:50 Jens Axboe [this message]
2009-09-11 11:50 ` [PATCH 1/4] writeback: merely wakeup flusher thread if work allocation fails for WB_SYNC_NONE Jens Axboe
2009-09-11 17:59 ` Christoph Hellwig
2009-09-11 11:50 ` [PATCH 2/4] Assign bdi in super_block Jens Axboe
2009-09-11 18:01 ` Christoph Hellwig
2009-09-11 18:12 ` Jens Axboe
2009-09-11 18:16 ` Christoph Hellwig
2009-09-11 11:50 ` [PATCH 3/4] writeback: only use bdi_writeback_all() for WB_SYNC_NONE writeout Jens Axboe
2009-09-11 18:09 ` Christoph Hellwig
2009-09-11 18:14 ` Jens Axboe
2009-09-13 18:20 ` Jens Axboe
2009-09-11 11:50 ` [PATCH 4/4] writeback: use RCU to protect bdi_list 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=1252669832-13553-1-git-send-email-jens.axboe@oracle.com \
--to=jens.axboe@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).