From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: ngupta@vflare.org, Christoph Hellwig <hch@infradead.org>,
akpm@linux-foundation.org
Cc: 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: Fri, 23 Jul 2010 06:58:03 -0700 (PDT) [thread overview]
Message-ID: <840b32ff-a303-468e-9d4e-30fc92f629f8@default> (raw)
In-Reply-To: <4C49468B.40307@vflare.org>
> Since zcache is now one of its use cases, I think the major
> objection that remains against cleancache is its intrusiveness
> -- in particular, need to change individual filesystems (even
> though one liners). Changes below should help avoid these
> per-fs changes and make it more self contained.
Hi Nitin --
I think my reply at http://lkml.org/lkml/2010/6/22/202 adequately
refutes the claim of intrusiveness (43 lines!). And FAQ #2 near
the end of the original posting at http://lkml.org/lkml/2010/6/21/411
explains why the per-fs "opt-in" approach is sensible and necessary.
CHRISTOPH AND ANDREW, if you disagree and your concerns have
not been resolved, please speak up.
Further, the maintainers of the changed filesystems have acked
the very minor cleancache patches; and maintainers of other
filesystems are not affected unless they choose to opt-in,
whereas these other filesystems MAY be affected with your
suggested changes to the patches.
So I think it's just a matter of waiting for the Linux wheels
to turn for a patch that (however lightly) touches a number of
maintainers' code, though I would very much welcome any
input on anything I can do to make those wheels turn faster.
Thanks,
Dan
--
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-23 13:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100621231809.GA11111@ca-server1.us.oracle.com>
2010-06-22 6:40 ` [PATCH V3 0/8] Cleancache: overview 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 [this message]
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
2010-06-21 23:18 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=840b32ff-a303-468e-9d4e-30fc92f629f8@default \
--to=dan.magenheimer@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=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;
as well as URLs for NNTP newsgroup(s).