From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Dave Hansen <dave@sr71.net>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
chris.mason@oracle.com, viro@zeniv.linux.org.uk,
akpm@linux-foundation.org, adilger@Sun.COM, tytso@mit.edu,
mfasheh@suse.com, 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,
ngupta@vflare.org, jeremy@goop.org, JBeulich@novell.com,
kurt.hackel@oracle.com, npiggin@suse.de,
dave.mccracken@oracle.com, riel@redhat.com, avi@redhat.com
Subject: Re: [PATCH V3 3/8] Cleancache: core ops functions and configuration
Date: Tue, 6 Jul 2010 16:51:21 -0400 [thread overview]
Message-ID: <20100706205121.GA32627@phenom.dumpdata.com> (raw)
In-Reply-To: <1277223988.9782.20.camel@nimitz>
On Tue, Jun 22, 2010 at 09:26:28AM -0700, Dave Hansen wrote:
> On Mon, 2010-06-21 at 16:19 -0700, Dan Magenheimer wrote:
> > --- linux-2.6.35-rc2/include/linux/cleancache.h 1969-12-31 17:00:00.000000000 -0700
> > +++ linux-2.6.35-rc2-cleancache/include/linux/cleancache.h 2010-06-21 14:45:18.000000000 -0600
> > @@ -0,0 +1,88 @@
> > +#ifndef _LINUX_CLEANCACHE_H
> > +#define _LINUX_CLEANCACHE_H
> > +
> > +#include <linux/fs.h>
> > +#include <linux/mm.h>
> > +
> > +struct cleancache_ops {
> > + int (*init_fs)(size_t);
> > + int (*init_shared_fs)(char *uuid, size_t);
> > + int (*get_page)(int, ino_t, pgoff_t, struct page *);
> > + void (*put_page)(int, ino_t, pgoff_t, struct page *);
> > + void (*flush_page)(int, ino_t, pgoff_t);
> > + void (*flush_inode)(int, ino_t);
> > + void (*flush_fs)(int);
> > +};
> > +
>
> How would someone go about testing this code? Is there an example
> cleancache implementation?
Dan,
Can you reference with a link or a git branch the patches that utilize
this?
And also mention that in the 0/X patch so that folks can reference your
cleancache implementation?
--
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-07-06 20:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 23:19 [PATCH V3 3/8] Cleancache: core ops functions and configuration Dan Magenheimer
2010-06-22 14:43 ` Christoph Hellwig
2010-06-22 15:13 ` Nitin Gupta
2010-06-22 16:20 ` Dan Magenheimer
2010-06-22 16:26 ` Dave Hansen
2010-07-06 20:51 ` Konrad Rzeszutek Wilk [this message]
2010-07-07 1:02 ` Nitin Gupta
2010-07-07 13:27 ` Konrad Rzeszutek Wilk
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=20100706205121.GA32627@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@novell.com \
--cc=adilger@Sun.COM \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=chris.mason@oracle.com \
--cc=dan.magenheimer@oracle.com \
--cc=dave.mccracken@oracle.com \
--cc=dave@sr71.net \
--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;
as well as URLs for NNTP newsgroup(s).