[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20101125123001.9bc75815.akpm@linux-foundation.org>
Date: Thu, 25 Nov 2010 12:30:01 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Boaz Harrosh <bharrosh@...asas.com>
Cc: Chris Mason <chris.mason@...cle.com>,
Nick Piggin <npiggin@...nel.dk>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Al Viro <viro@...iv.linux.org.uk>,
linux-ext4 <linux-ext4@...r.kernel.org>,
linux-btrfs <linux-btrfs@...r.kernel.org>,
Jan Kara <jack@...e.cz>, Eric Sandeen <sandeen@...hat.com>,
"Theodore Ts'o" <tytso@....edu>
Subject: Re: [patch] fs: fix deadlocks in writeback_if_idle
On Thu, 25 Nov 2010 11:41:50 +0200 Boaz Harrosh <bharrosh@...asas.com> wrote:
> On 11/25/2010 12:47 AM, Andrew Morton wrote:
> > On Tue, 23 Nov 2010 07:34:07 -0500
> > Chris Mason <chris.mason@...cle.com> wrote:
> >
> >> For btrfs there's only one bdi per SB, but for most everyone else a disk
> >> with a bunch of partitions is going to have multiple filesystems on the
> >> same bdi.
> >
> > um, please explain why that wasn't idiotic? The BDI is a
> > representation of a backing device and it's *supposed* to provide
> > visibility into what's happening against other partitions on the same
> > device. Creating a BDI per SB (it didn't even occur to me to think
> > that a filesystem was even able to do this) breaks that.
> >
>
> In btrfs an SB my span multiple partitions. How else can it be solved?
Associate a number of bdi's with the superblock. If necessary, convert
core kernel to operate on groups of BDI's. Which shouldn't be too hard
given that core kernel already does this, for MD.
ie: something which faithfully models what is actually going on, rather
than simply bending reality.
--
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