linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Minchan Kim <minchan@kernel.org>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	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>, Bob Liu <bob.liu@oracle.com>,
	Shuah Khan <shuah@gonehiking.org>
Subject: Re: zsmalloc defrag (Was: [PATCH] mm: remove compressed copy from zram in-memory)
Date: Tue, 9 Apr 2013 10:36:06 +0900	[thread overview]
Message-ID: <20130409013606.GC3467@blaptop> (raw)
In-Reply-To: <20130409012719.GB3467@blaptop>

On Tue, Apr 09, 2013 at 10:27:19AM +0900, Minchan Kim wrote:
> Hi Dan,
> 
> On Mon, Apr 08, 2013 at 09:32:38AM -0700, Dan Magenheimer wrote:
> > > 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
> 
> What I can say now about is only just a word "Compaction".
> As you know, zsmalloc has a transparent handle so we can do whatever
> under user. Of course, there is a tradeoff between performance 
> and memory efficiency. I'm biased to latter for embedded usecase.
> 
> And I might post it because as you know well, zsmalloc

Incomplete sentense,

I might not post it until promoting zsmalloc because as you know well,
zsmalloc/zram's all new stuffs are blocked into staging tree.
Even if we could add it into staging, as you know well, staging is where
every mm guys ignore so we end up needing another round to promote it. sigh.

I hope it gets better after LSF/MM.

-- 
Kind regards,
Minchan Kim

  reply	other threads:[~2013-04-09  1:36 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 ` zsmalloc defrag (Was: [PATCH] mm: remove compressed copy from zram in-memory) Dan Magenheimer
2013-04-09  1:27   ` Minchan Kim
2013-04-09  1:36     ` Minchan Kim [this message]
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=20130409013606.GC3467@blaptop \
    --to=minchan@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bob.liu@oracle.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=hughd@google.com \
    --cc=konrad@darnok.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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).