[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100723140440.GA12423@infradead.org>
Date: Fri, 23 Jul 2010 10:04:40 -0400
From: Christoph Hellwig <hch@...radead.org>
To: Dan Magenheimer <dan.magenheimer@...cle.com>
Cc: ngupta@...are.org, Christoph Hellwig <hch@...radead.org>,
akpm@...ux-foundation.org, Chris Mason <chris.mason@...cle.com>,
viro@...iv.linux.org.uk, adilger@....com, tytso@....edu,
mfasheh@...e.com, Joel Becker <joel.becker@...cle.com>,
matthew@....cx, linux-btrfs@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-ext4@...r.kernel.org, ocfs2-devel@....oracle.com,
linux-mm@...ck.org, jeremy@...p.org, JBeulich@...ell.com,
Kurt Hackel <kurt.hackel@...cle.com>, npiggin@...e.de,
Dave Mccracken <dave.mccracken@...cle.com>, riel@...hat.com,
avi@...hat.com, Konrad Wilk <konrad.wilk@...cle.com>
Subject: Re: [PATCH V3 0/8] Cleancache: overview
On Fri, Jul 23, 2010 at 06:58:03AM -0700, Dan Magenheimer wrote:
> CHRISTOPH AND ANDREW, if you disagree and your concerns have
> not been resolved, please speak up.
Anything that need modification of a normal non-shared fs is utterly
broken and you'll get a clear NAK, so the propsal before is a good
one. There's a couple more issues like the still weird prototypes,
e.g. and i_ino might not be enoug to uniquely identify an inode
on serveral filesystems that use 64-bit inode inode numbers on 32-bit
systems. Also making the ops vector global is just a bad idea.
There is nothing making this sort of caching inherently global.
--
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