From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Jan Kara <jack@suse.cz>
Cc: Jens Axboe <jens.axboe@oracle.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
chris.mason@oracle.com, hch@infradead.org, tytso@mit.edu,
akpm@linux-foundation.org
Subject: Re: [PATCH 2/7] Assign bdi in super_block
Date: Tue, 15 Sep 2009 09:16:41 -0400 [thread overview]
Message-ID: <1253020601.4456.1.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <20090915101457.GE12169@duck.suse.cz>
On Tue, 2009-09-15 at 12:14 +0200, Jan Kara wrote:
> On Mon 14-09-09 20:36:54, Jens Axboe wrote:
> > No, that should work fine. NFS already works fine with the bdi flusher
> > threads, so you should just point it at that bdi.
> But will it really work well? I mean if we sync the superblock on the
> client, it will sync only the private BDI. So it won't sync any directory
> inodes because they are on the default_backing_dev_info (NFS leaves
> sb->s_bdev at NULL).
All directory related operations (link, rename, create, ...) are fully
synchronous in NFS. There should be no need to set up anything to
synchronise directory inodes.
Cheers
Trond
next prev parent reply other threads:[~2009-09-15 13:16 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 [this message]
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
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=1253020601.4456.1.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--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=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
all inboxes | Powered by JetHome®