From: Christoph Hellwig <hch@lst.de>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: Jan Kara <jack@suse.cz>, Christoph Hellwig <hch@infradead.org>,
Al Viro <viro@ZenIV.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Trond Myklebust <Trond.Myklebust@netapp.com>,
Benny Halevy <bhalevy@panasas.com>
Subject: Re: [RFC] vfs/inode: For none-block-based filesystems default to sb->s_bdi
Date: Wed, 6 Oct 2010 04:55:17 -0400 [thread overview]
Message-ID: <20101006085517.GB7295@lst.de> (raw)
In-Reply-To: <4CAB4473.1070408@panasas.com>
On Tue, Oct 05, 2010 at 11:29:55AM -0400, Boaz Harrosh wrote:
> If you are right and inode->i_mapping.backing_dev_info will only be used for bdev
> inodes, then I prefer if it would be NULL by default and not pointing to
> &default_backing_dev_info. Will that be fixed as well?
It's been pointing to default_backing_dev_info since long before we got
the per-bdi writeback. Once the writeback bits are're back to what we used
the BDI for before:
- set VM readahead parameters
- deal with per-backingdev congestion/unplugging
- a couple of VM statistics
in general all these really should point to the same for a normal filesystem,
and at least point to the same in a group even for "strange" filesystems
that have multiple backing devices. The BDI still is a rather strangely
defined beast, and so far all my attempts to make sense of it have failed.
prev parent reply other threads:[~2010-10-06 20:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 21:46 [RFC] vfs/inode: For none-block-based filesystems default to sb->s_bdi Boaz Harrosh
2010-10-04 22:02 ` Boaz Harrosh
2010-10-05 8:32 ` Jan Kara
2010-10-05 13:53 ` Boaz Harrosh
2010-10-05 13:54 ` Boaz Harrosh
2010-10-05 15:12 ` Jan Kara
2010-10-05 15:09 ` Jan Kara
2010-10-05 15:29 ` Boaz Harrosh
2010-10-05 15:50 ` Jan Kara
2010-10-06 8:55 ` Christoph Hellwig [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=20101006085517.GB7295@lst.de \
--to=hch@lst.de \
--cc=Trond.Myklebust@netapp.com \
--cc=bhalevy@panasas.com \
--cc=bharrosh@panasas.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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.