From: Jens Axboe <jens.axboe@oracle.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
chris.mason@oracle.com, david@fromorbit.com, hch@infradead.org,
tytso@mit.edu, akpm@linux-foundation.org
Subject: Re: [PATCH 1/8] writeback: get rid of generic_sync_sb_inodes() export
Date: Wed, 2 Sep 2009 12:26:26 +0200 [thread overview]
Message-ID: <20090902102626.GR12579@kernel.dk> (raw)
In-Reply-To: <20090902101333.GB17842@duck.novell.com>
On Wed, Sep 02 2009, Jan Kara wrote:
> On Wed 02-09-09 10:42:40, Jens Axboe wrote:
> > This adds two new exported functions:
> >
> > - sync_inodes_sb(), which writes out dirty inodes on a super_block, and
> > - sync_inodes_sb_wait(), which does the same but also waits for IO
> > completion.
> This is a nice cleanup. I only find the name sync_inodes_sb() slightly
> misleading and the comment by that function as well. The name should rather
> be something like writeback_inodes_sb() (and sync_inodes_sb_wait() could
> stay just sync_inodes_sb()) - the writeback it does does not really
> guarantee anything. For example it can skip inodes or pages it does not
> like for some reason. What that function really does is - try to write some
> dirty pages on that superblock and don't try too hard.
> I don't insist on the renaming of the function but I really thing the
> comment should be improved.
I don't disagree, I was a bit torn on the naming as well. I will make
that change, thanks for the feedback!
I'd really like your feedback on the pin_sb_for_writeback() stuff too,
since that is the contentious bit. And, this goes for others as well,
I'd appreciate any reviewed-by and/or acked-by on patches.
--
Jens Axboe
next prev parent reply other threads:[~2009-09-02 10:26 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 8:42 [PATCH 0/8] Per-bdi writeback flusher threads v17 Jens Axboe
2009-09-02 8:42 ` [PATCH 1/8] writeback: get rid of generic_sync_sb_inodes() export Jens Axboe
2009-09-02 10:13 ` Jan Kara
2009-09-02 10:26 ` Jens Axboe [this message]
2009-09-02 14:01 ` Jan Kara
2009-09-02 8:42 ` [PATCH 2/8] writeback: move dirty inodes from super_block to backing_dev_info Jens Axboe
2009-09-04 2:46 ` Christoph Hellwig
2009-09-04 2:50 ` Christoph Hellwig
2009-09-04 7:19 ` Jens Axboe
2009-09-04 2:56 ` Christoph Hellwig
2009-09-04 6:53 ` Jens Axboe
2009-09-04 15:43 ` Christoph Hellwig
2009-09-06 18:43 ` Jens Axboe
2009-09-08 18:44 ` Christoph Hellwig
2009-09-11 7:47 ` Jens Axboe
2009-09-02 8:42 ` [PATCH 3/8] writeback: switch to per-bdi threads for flushing data Jens Axboe
2009-09-02 8:42 ` [PATCH 4/8] writeback: get rid of pdflush completely Jens Axboe
2009-09-02 8:42 ` [PATCH 5/8] writeback: add some debug inode list counters to bdi stats Jens Axboe
2009-09-02 8:42 ` [PATCH 6/8] writeback: add name to backing_dev_info Jens Axboe
2009-09-02 8:42 ` [PATCH 7/8] writeback: check for registered bdi in flusher add and inode dirty Jens Axboe
2009-09-02 8:42 ` [PATCH 8/8] vm: Add an tuning knob for vm.max_writeback_pages Jens Axboe
2009-09-04 7:46 [PATCH 0/8] Per-bdi writeback flusher threads v18 Jens Axboe
2009-09-04 7:46 ` [PATCH 1/8] writeback: get rid of generic_sync_sb_inodes() export Jens Axboe
2009-09-04 8:28 ` Jan Kara
2009-09-04 11:59 ` Jens Axboe
2009-09-08 9:23 [PATCH 0/8] Per-bdi writeback flusher threads v19 Jens Axboe
2009-09-08 9:23 ` [PATCH 1/8] writeback: get rid of generic_sync_sb_inodes() export Jens Axboe
2009-09-08 10:27 ` Artem Bityutskiy
2009-09-08 10:41 ` Jens Axboe
2009-09-08 10:52 ` Artem Bityutskiy
2009-09-08 10:57 ` Jens Axboe
2009-09-08 11:01 ` Artem Bityutskiy
2009-09-08 11:05 ` Jens Axboe
2009-09-08 11:31 ` Artem Bityutskiy
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=20090902102626.GR12579@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome