From: Andrew Morton <akpm@linux-foundation.org>
To: ngupta@vflare.org
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
Christoph Lameter <cl@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] compcache documentation
Date: Sat, 21 Mar 2009 03:26:36 -0700 [thread overview]
Message-ID: <20090321032636.fdeae224.akpm@linux-foundation.org> (raw)
In-Reply-To: <49C3A4B0.3050503@vflare.org>
On Fri, 20 Mar 2009 19:44:08 +0530 Nitin Gupta <ngupta@vflare.org> wrote:
> ...
>
> + backing_dev: This is block device to be used as backing store for compcache.
> + It must be a valid swap partition. We move data to this device when we
> + encounter incompressible page or memlimit is reached. TODO: we may also
> + move some pages from compcache to this device in case system is really
> + low on memory.
> + This device is not directly visible to kernel as a swap device
> + (/proc/swaps will only show /dev/ramzswap0 and not this device).
> + Managing this backing device is the job of compcache module.
hrm, OK, it kinda/sorta/maybe might be a little bit like a "compressed
cache". But if someone comes up with a real compressed cache (ie:
pagecache) then they'll want their name back.
Also, the kernel already has a widespread and well-established "backing
device" concept, in include/linux/backing-dev.h. This new feature's
poaching of that identifier is a bit confusing. It would be nice to do a
wholesale rename if possible. secondary_dev? nv_dev?
next prev parent reply other threads:[~2009-03-21 10:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 14:07 [PATCH 0/3] compressed in-memory swapping take2 Nitin Gupta
2009-03-20 14:10 ` [PATCH 1/3] compressed RAM block device Nitin Gupta
2009-03-20 14:12 ` [PATCH 2/3] xvmalloc memory allocator Nitin Gupta
2009-03-20 14:57 ` Christoph Lameter
2009-03-20 16:24 ` Nitin Gupta
2009-03-20 17:40 ` Christoph Lameter
2009-03-20 19:01 ` Pekka Enberg
2009-03-20 19:43 ` Nitin Gupta
2009-03-21 10:21 ` Andrew Morton
2009-03-21 12:12 ` Nitin Gupta
2009-03-21 12:24 ` Andrew Morton
2009-03-21 13:14 ` Nitin Gupta
2009-03-21 16:21 ` Pekka Enberg
2009-03-21 17:36 ` Nitin Gupta
2009-03-20 14:14 ` [PATCH 3/3] compcache documentation Nitin Gupta
2009-03-21 10:26 ` Andrew Morton [this message]
2009-03-21 12:31 ` Nitin Gupta
2009-03-21 12:55 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2008-04-08 9:29 [PATCH 0/3] compcache: compressed caching v2 Nitin Gupta
2008-04-08 9:36 ` [PATCH 3/3] compcache: documentation Nitin Gupta
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=20090321032636.fdeae224.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ngupta@vflare.org \
--cc=penberg@cs.helsinki.fi \
/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