From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Minchan Kim <minchan@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Hugh Dickins <hughd@google.com>,
Seth Jennings <sjenning@linux.vnet.ibm.com>,
Nitin Gupta <ngupta@vflare.org>,
Konrad Rzeszutek Wilk <konrad@darnok.org>,
Shaohua Li <shli@kernel.org>,
Dan Magenheimer <dan.magenheimer@oracle.com>,
Bob Liu <bob.liu@oracle.com>, Shuah Khan <shuah@gonehiking.org>
Subject: zsmalloc defrag (Was: [PATCH] mm: remove compressed copy from zram in-memory)
Date: Mon, 8 Apr 2013 09:32:38 -0700 (PDT) [thread overview]
Message-ID: <f3c8ef05-a880-47db-86dd-156038fc7d0f@default> (raw)
In-Reply-To: <<1365400862-9041-1-git-send-email-minchan@kernel.org>>
> From: Minchan Kim [mailto:minchan@kernel.org]
> Sent: Monday, April 08, 2013 12:01 AM
> Subject: [PATCH] mm: remove compressed copy from zram in-memory
(patch removed)
> Fragment ratio is almost same but memory consumption and compile time
> is better. I am working to add defragment function of zsmalloc.
Hi Minchan --
I would be very interested in your design thoughts on
how you plan to add defragmentation for zsmalloc. In
particular, I am wondering if your design will also
handle the requirements for zcache (especially for
cleancache pages) and perhaps also for ramster.
In https://lkml.org/lkml/2013/3/27/501 I suggested it
would be good to work together on a common design, but
you didn't reply. Are you thinking that zsmalloc
improvements should focus only on zram, in which case
we may -- and possibly should -- end up with a different
allocator for frontswap-based/cleancache-based compression
in zcache (and possibly zswap)?
I'm just trying to determine if I should proceed separately
with my design (with Bob Liu, who expressed interest) or if
it would be beneficial to work together.
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 parent reply other threads:[~2013-04-08 16:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<1365400862-9041-1-git-send-email-minchan@kernel.org>
2013-04-08 16:32 ` Dan Magenheimer [this message]
2013-04-09 1:27 ` zsmalloc defrag (Was: [PATCH] mm: remove compressed copy from zram in-memory) Minchan Kim
2013-04-09 1:36 ` Minchan Kim
2013-04-09 20:37 ` Dan Magenheimer
2013-04-10 0:54 ` Minchan Kim
2013-04-11 17:53 ` Dan Magenheimer
2013-04-09 20:52 ` Seth Jennings
2013-04-10 0:58 ` Minchan Kim
2013-04-11 17:56 ` Dan Magenheimer
2013-04-11 17:30 ` Dan Magenheimer
2013-04-09 20:25 ` Dan Magenheimer
2013-04-10 0:50 ` Minchan Kim
2013-04-10 1:07 ` Ric Mason
2013-04-11 17:46 ` Dan Magenheimer
2013-04-10 1:03 ` Ric Mason
2013-04-08 6:01 [PATCH] mm: remove compressed copy from zram in-memory Minchan Kim
2013-04-08 21:17 ` Andrew Morton
2013-04-09 1:02 ` Minchan Kim
2013-04-09 5:36 ` Ric Mason
2013-04-09 23:40 ` Minchan Kim
2013-04-09 19:54 ` Andrew Morton
2013-04-10 0:16 ` Minchan Kim
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=f3c8ef05-a880-47db-86dd-156038fc7d0f@default \
--to=dan.magenheimer@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bob.liu@oracle.com \
--cc=hughd@google.com \
--cc=konrad@darnok.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=shli@kernel.org \
--cc=shuah@gonehiking.org \
--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).