From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: 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 0/8] Cleancache: overview
Date: Tue, 6 Jul 2010 16:58:20 -0400 [thread overview]
Message-ID: <20100706205820.GB32627@phenom.dumpdata.com> (raw)
In-Reply-To: <20100621231809.GA11111@ca-server1.us.oracle.com>
On Mon, Jun 21, 2010 at 04:18:09PM -0700, Dan Magenheimer wrote:
> [PATCH V3 0/8] Cleancache: overview
Dan,
Two comments:
- Mention where one can get the implementor of the cleancache API.
Either a link to where the patches reside or a git branch.
If you need pointers on branch names:
http://lkml.org/lkml/2010/6/7/269
- Point out the presentation you did on this. It has an excellent
overview of how this API works, and most importantly: a) images
and b). performance numbers.
Otherwise, please consider all of these patches to have
Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
tag.
--
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:59 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 [this message]
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
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=20100706205820.GB32627@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=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