From: Kyungmin Park <kmpark@infradead.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Bob Liu <bob.liu@oracle.com>,
Greg KH <gregkh@linuxfoundation.org>, Bob Liu <lliubbo@gmail.com>,
linux-mm@kvack.org, ngupta@vflare.org, akpm@linux-foundation.org,
sjenning@linux.vnet.ibm.com, riel@redhat.com, mgorman@suse.de,
p.sarna@partner.samsung.com, barry.song@csr.com,
penberg@kernel.org
Subject: Re: [PATCH v2 0/4] zcache: a compressed file page cache
Date: Mon, 12 Aug 2013 21:25:05 +0900 [thread overview]
Message-ID: <CAH9JG2VhN5-D132d0L0s8z4wQshfCeP5=aVWQLCAz7SP8HHyNg@mail.gmail.com> (raw)
In-Reply-To: <20130812121908.GA3196@phenom.dumpdata.com>
On Mon, Aug 12, 2013 at 9:19 PM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Tue, Aug 06, 2013 at 10:24:20PM +0800, Bob Liu wrote:
>> Hi Greg,
>>
>> On 08/06/2013 09:58 PM, Greg KH wrote:
>> > On Tue, Aug 06, 2013 at 07:36:13PM +0800, Bob Liu wrote:
>> >> Dan Magenheimer extended zcache supporting both file pages and anonymous pages.
>> >> It's located in drivers/staging/zcache now. But the current version of zcache is
>> >> too complicated to be merged into upstream.
>> >
>> > Really? If this is so, I'll just go delete zcache now, I don't want to
>> > lug around dead code that will never be merged.
>> >
>>
>> Zcache in staging have a zbud allocation which is almost the same as
>> mm/zbud.c but with different API and have a frontswap backend like
>> mm/zswap.c.
>> So I'd prefer reuse mm/zbud.c and mm/zswap.c for a generic memory
>> compression solution.
>> Which means in that case, zcache in staging = mm/zswap.c + mm/zcache.c +
>> mm/zbud.c.
>>
>> But I'm not sure if there are any existing users of zcache in staging,
>> if not I can delete zcache from staging in my next version of this
>> mm/zcache.c series.
>
> I think the Samsung folks are using it (zcache).
I'm not sure, but, at least, my team doesn't use it at now.
Thank you,
Kyungmin Park
--
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:[~2013-08-12 12:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 11:36 [PATCH v2 0/4] zcache: a compressed file page cache Bob Liu
2013-08-06 11:36 ` [PATCH v2 1/4] mm: zcache: add core files Bob Liu
2013-08-06 11:36 ` [PATCH v2 2/4] zcache: staging: %s/ZCACHE/ZCACHE_OLD Bob Liu
2013-08-06 11:36 ` [PATCH v2 3/4] mm: zcache: add evict zpages supporting Bob Liu
2013-08-06 11:36 ` [PATCH v2 4/4] mm: add WasActive page flag Bob Liu
2013-08-13 6:01 ` Pekka Enberg
2013-08-13 13:50 ` Bob Liu
2013-08-06 13:58 ` [PATCH v2 0/4] zcache: a compressed file page cache Greg KH
2013-08-06 14:24 ` Bob Liu
2013-08-12 12:19 ` Konrad Rzeszutek Wilk
2013-08-12 12:25 ` Kyungmin Park [this message]
2013-08-12 12:30 ` Wanpeng Li
2013-08-12 13:23 ` Konrad Rzeszutek Wilk
2013-08-12 22:10 ` Greg KH
2013-08-12 12:30 ` Wanpeng Li
2013-08-09 8:03 ` Bob Liu
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='CAH9JG2VhN5-D132d0L0s8z4wQshfCeP5=aVWQLCAz7SP8HHyNg@mail.gmail.com' \
--to=kmpark@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=barry.song@csr.com \
--cc=bob.liu@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-mm@kvack.org \
--cc=lliubbo@gmail.com \
--cc=mgorman@suse.de \
--cc=ngupta@vflare.org \
--cc=p.sarna@partner.samsung.com \
--cc=penberg@kernel.org \
--cc=riel@redhat.com \
--cc=sjenning@linux.vnet.ibm.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).