[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20121101224216.GA31937@quack.suse.cz>
Date: Thu, 1 Nov 2012 23:42:16 +0100
From: Jan Kara <jack@...e.cz>
To: Boaz Harrosh <bharrosh@...asas.com>
Cc: Jan Kara <jack@...e.cz>,
"Darrick J. Wong" <darrick.wong@...cle.com>,
NeilBrown <neilb@...e.de>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Theodore Ts'o <tytso@....edu>,
linux-ext4 <linux-ext4@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [RFC PATCH 1/2] bdi: Create a flag to indicate that a backing
device needs stable page writes
On Thu 01-11-12 10:24:48, Boaz Harrosh wrote:
> On 11/01/2012 01:59 AM, Jan Kara wrote:
> <>
> > (all block device inodes share one superblock).
> >
>
> Really? that is not so good is it, for other obvious reasons.
> Why is it not one superblock per BDI? That would be more obvious
> to me.
>
> > Thoughts?
>
> It's a really bad design. I think it is worth fixing. For the above
> problem, as well as a much better fit with our current thread-per-bdi,
> and the rest of the Kernel model. No?
So the fact that there is one superblock of virtual filesystem containing
all block device inodes is inconvenient at times (that's why we have to
have inode_to_bdi() function in fs/fs-writeback.c) but OTOH you cannot
really attach these virtual block device inodes (note that these are
different from an inode for an object say /dev/sda in the filesystem)
anywhere else and having one sb per block device would really be an
overkill.
Honza
--
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists