From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: balbir@linux.vnet.ibm.com
Cc: Christoph Hellwig <hch@infradead.org>,
Boaz Harrosh <bharrosh@panasas.com>,
ngupta@vflare.org, akpm@linux-foundation.org,
Chris Mason <chris.mason@oracle.com>,
viro@zeniv.linux.org.uk,
Andreas Dilger <andreas.dilger@oracle.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>,
Dave Mccracken <dave.mccracken@oracle.com>,
riel@redhat.com, Konrad Wilk <konrad.wilk@oracle.com>,
Mel Gorman <mel@csn.ul.ie>, Ying Han <yinghan@google.com>,
Greg Thelen <gthelen@google.com>,
npiggin@kernel.dk
Subject: RE: cleancache followup from LSF10/MM summit
Date: Tue, 24 Aug 2010 13:42:55 -0700 (PDT) [thread overview]
Message-ID: <43348bbd-649d-47db-8edd-c5cb08187f19@default> (raw)
In-Reply-To: <20100824142718.GA24164@balbir.in.ibm.com>
Hi Balbir --
Thanks for reviewing!
> 1. Can't this be done at the MM layer - why the filesystem hooks? Is
> it to enable faster block devices in the reclaim hierarchy?
This is explained in FAQ #2 in: http://lkml.org/lkml/2010/6/21/411
If I misunderstood your question or the FAQ doesn't answer it, please
let me know.
> 2. I don't see a mention of slabcache in your approach, reclaim free
> pages or freeing potentially free slab pages.
Cleancache works on clean mapped pages that are reclaimed ("evicted")
due to (guest) memory pressure but later would result in a refault.
The decision of what pages to reclaim are left entirely to the
(guest) kernel, and the "backend" (zcache or Xen tmem) dynamically
decides how many clean evicted pages to retain based on dynamic
factors that are unknowable to the (guest) kernel (such as compression
ratios for zcache and available fallow memory for Xen tmem).
I'm not sure I see how this could apply to slabcache (and
I couldn't find anything in your OLS paper that refers to it),
but if you have some ideas, let's discuss (offlist?).
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>
prev parent reply other threads:[~2010-08-24 20:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 15:14 cleancache followup from LSF10/MM summit Dan Magenheimer
2010-08-24 14:27 ` Balbir Singh
2010-08-24 20:42 ` Dan Magenheimer [this message]
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=43348bbd-649d-47db-8edd-c5cb08187f19@default \
--to=dan.magenheimer@oracle.com \
--cc=JBeulich@novell.com \
--cc=akpm@linux-foundation.org \
--cc=andreas.dilger@oracle.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=bharrosh@panasas.com \
--cc=chris.mason@oracle.com \
--cc=dave.mccracken@oracle.com \
--cc=gthelen@google.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=mel@csn.ul.ie \
--cc=mfasheh@suse.com \
--cc=ngupta@vflare.org \
--cc=npiggin@kernel.dk \
--cc=ocfs2-devel@oss.oracle.com \
--cc=riel@redhat.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=yinghan@google.com \
/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).