From: Andreas Dilger <andreas.dilger@oracle.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Boaz Harrosh <bharrosh@panasas.com>,
Christoph Hellwig <hch@infradead.org>,
ngupta@vflare.org, akpm@linux-foundation.org,
Chris Mason <chris.mason@oracle.com>,
viro@zeniv.linux.org.uk, adilger@sun.com, tytso@mit.edu,
mfasheh@suse.com, Joel Becker <joel.becker@oracle.com>,
matthew@wil.cx, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org, ocfs2-devel@oss.oracle.com,
linux-mm@kvack.org, jeremy@goop.org, JBeulich@novell.com,
Kurt Hackel <kurt.hackel@oracle.com>,
npiggin@suse.de, Dave Mccracken <dave.mccracken@oracle.com>,
riel@redhat.com, avi@redhat.com,
Konrad Wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH V3 0/8] Cleancache: overview
Date: Tue, 3 Aug 2010 12:34:19 -0600 [thread overview]
Message-ID: <22A6238E-0BA4-4AB9-A4FA-28B206A47513@oracle.com> (raw)
In-Reply-To: <a7f4db53-c348-4cff-8762-7ea4031e4813@default>
On 2010-08-03, at 11:35, Dan Magenheimer wrote:
> - The FS should be block-device-based (e.g. a ram-based FS
> such as tmpfs should not enable cleancache)
When you say "block device based", does this exclude network filesystems? It would seem cleancache, like fscache, is actually best suited to high-latency network filesystems.
> - To ensure coherency/correctness, inode numbers must be unique
> (e.g. no emulating 64-bit inode space on 32-bit inode numbers)
Does it need to be restricted to inode numbers at all (i.e. can it use an opaque internal identifier like the NFS file handle)? Disallowing cleancache on a filesystem that uses 64-bit (or larger) inodes on a 32-bit system reduces its usefulness.
Cheers, Andreas
--
Andreas Dilger
Lustre Technical Lead
Oracle Corporation Canada Inc.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-08-03 18:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 23:18 Dan Magenheimer
2010-06-22 6:40 ` Christoph Hellwig
2010-07-06 20:58 ` Konrad Rzeszutek Wilk
2010-07-23 7:36 ` Nitin Gupta
2010-07-23 8:16 ` Minchan Kim
2010-07-23 14:56 ` Nitin Gupta
2010-07-23 8:17 ` Minchan Kim
2010-07-23 13:58 ` Dan Magenheimer
2010-07-23 14:04 ` Christoph Hellwig
2010-07-23 14:44 ` Dan Magenheimer
2010-07-23 15:05 ` Nitin Gupta
2010-07-23 17:43 ` Dan Magenheimer
2010-07-23 17:37 ` Dan Magenheimer
2010-07-23 18:36 ` Nitin Gupta
2010-07-23 21:17 ` Dan Magenheimer
2010-08-03 16:22 ` Boaz Harrosh
2010-08-03 17:35 ` Dan Magenheimer
2010-08-03 18:34 ` Andreas Dilger [this message]
2010-08-03 19:09 ` Dan Magenheimer
[not found] <20100621231809.GA11111@ca-server1.us.oracle.com4C49468B.40307@vflare.org>
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=22A6238E-0BA4-4AB9-A4FA-28B206A47513@oracle.com \
--to=andreas.dilger@oracle.com \
--cc=JBeulich@novell.com \
--cc=adilger@sun.com \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=bharrosh@panasas.com \
--cc=chris.mason@oracle.com \
--cc=dan.magenheimer@oracle.com \
--cc=dave.mccracken@oracle.com \
--cc=hch@infradead.org \
--cc=jeremy@goop.org \
--cc=joel.becker@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=kurt.hackel@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew@wil.cx \
--cc=mfasheh@suse.com \
--cc=ngupta@vflare.org \
--cc=npiggin@suse.de \
--cc=ocfs2-devel@oss.oracle.com \
--cc=riel@redhat.com \
--cc=tytso@mit.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox