From: Andreas Dilger <adilger@sun.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Chris Mason <chris.mason@oracle.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Theodore Ts'o <tytso@mit.edu>,
mfasheh@suse.com, Joel Becker <joel.becker@oracle.com>,
Matthew Wilcox <matthew@wil.cx>,
linux-btrfs@vger.kernel.org,
"linux-kernel@vger.kernel.org Mailinglist"
<linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org,
linux-ext4 development <linux-ext4@vger.kernel.org>,
ocfs2-devel@oss.oracle.com, linux-mm@kvack.org,
ngupta@vflare.org, Jeremy Fitzhardinge <jeremy@goop.org>,
JBeulich@novell.com, kurt.hackel@oracle.com,
Nick Piggin <npiggin@suse.de>,
dave.mccracken@oracle.com, Rik van Riel <riel@redhat.com>
Subject: Re: Cleancache [PATCH 6/7] (was Transcendent Memory): ext4 hook
Date: Wed, 28 Apr 2010 17:08:54 -0600 [thread overview]
Message-ID: <8EEE8A6D-343A-4514-BFC8-1EFEDE180B70@sun.com> (raw)
In-Reply-To: <20100422132929.GA27380@ca-server1.us.oracle.com>
On 2010-04-22, at 07:29, Dan Magenheimer wrote:
> Cleancache [PATCH 6/7] (was Transcendent Memory): ext4 hook
>
> Filesystems must explicitly enable cleancache. For ext4,
> all other cleancache hooks are in the VFS layer.
>
> Signed-off-by: Dan Magenheimer <dan.magenheimer@oracle.com>
Given the minimal changes being done to ext3/ext4, I don't have any objection to this. Being able to hook ext4 into SSDs for hierarchical caching is something that will become increasingly important for huge ext4 filesystems.
Acked-by: Andreas Dilger <adilger@sun.com>
> Diffstat:
> super.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> --- linux-2.6.34-rc5/fs/ext4/super.c 2010-04-19 17:29:56.000000000 -0600
> +++ linux-2.6.34-rc5-cleancache/fs/ext4/super.c 2010-04-21 10:13:00.000000000 -0600
> @@ -39,6 +39,7 @@
> #include <linux/ctype.h>
> #include <linux/log2.h>
> #include <linux/crc16.h>
> +#include <linux/cleancache.h>
> #include <asm/uaccess.h>
>
> #include "ext4.h"
> @@ -1784,6 +1785,7 @@ static int ext4_setup_super(struct super
> EXT4_INODES_PER_GROUP(sb),
> sbi->s_mount_opt);
>
> + sb->cleancache_poolid = cleancache_init_fs(PAGE_SIZE);
> return res;
> }
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of 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-04-28 23:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 13:29 Dan Magenheimer
2010-04-28 23:08 ` Andreas Dilger [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-22 12:15 Dan Magenheimer
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=8EEE8A6D-343A-4514-BFC8-1EFEDE180B70@sun.com \
--to=adilger@sun.com \
--cc=JBeulich@novell.com \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=dan.magenheimer@oracle.com \
--cc=dave.mccracken@oracle.com \
--cc=jeremy@goop.org \
--cc=joel.becker@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