All of lore.kernel.org
 help / color / mirror / Atom feed
From: Minchan Kim <minchan@kernel.org>
To: Vitaly Wool <vitalywool@gmail.com>
Cc: Seth Jennings <sjennings@variantweb.net>,
	Dan Streetman <ddstreet@ieee.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Linux-MM <linux-mm@kvack.org>
Subject: Re: [PATCH v2] zbud: allow up to PAGE_SIZE allocations
Date: Fri, 25 Sep 2015 17:50:02 +0900	[thread overview]
Message-ID: <20150925085002.GA17075@blaptop> (raw)
In-Reply-To: <20150925084617.GA23340@blaptop>

On Fri, Sep 25, 2015 at 05:47:13PM +0900, Minchan Kim wrote:
> On Fri, Sep 25, 2015 at 10:17:54AM +0200, Vitaly Wool wrote:
> > <snip>
> > > I already said questions, opinion and concerns but anything is not clear
> > > until now. Only clear thing I could hear is just "compaction stats are
> > > better" which is not enough for me. Sorry.
> > >
> > > 1) https://lkml.org/lkml/2015/9/15/33
> > > 2) https://lkml.org/lkml/2015/9/21/2
> > 
> > Could you please stop perverting the facts, I did answer to that:
> > https://lkml.org/lkml/2015/9/21/753.
> > 
> > Apart from that, an opinion is not necessarily something I would
> > answer. Concerns about zsmalloc are not in the scope of this patch's
> > discussion. If you have any concerns regarding this particular patch,
> > please let us know.
> 
> Yes, I don't want to interrupt zbud thing which is Seth should maintain
> and I respect his decision but the reason I nacked is you said this patch
> aims for supporing zbud into zsmalloc for determinism.
                               zram

Sorry for the typo.
                

--
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>

WARNING: multiple messages have this Message-ID (diff)
From: Minchan Kim <minchan@kernel.org>
To: Vitaly Wool <vitalywool@gmail.com>
Cc: Seth Jennings <sjennings@variantweb.net>,
	Dan Streetman <ddstreet@ieee.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Linux-MM <linux-mm@kvack.org>
Subject: Re: [PATCH v2] zbud: allow up to PAGE_SIZE allocations
Date: Fri, 25 Sep 2015 17:50:02 +0900	[thread overview]
Message-ID: <20150925085002.GA17075@blaptop> (raw)
In-Reply-To: <20150925084617.GA23340@blaptop>

On Fri, Sep 25, 2015 at 05:47:13PM +0900, Minchan Kim wrote:
> On Fri, Sep 25, 2015 at 10:17:54AM +0200, Vitaly Wool wrote:
> > <snip>
> > > I already said questions, opinion and concerns but anything is not clear
> > > until now. Only clear thing I could hear is just "compaction stats are
> > > better" which is not enough for me. Sorry.
> > >
> > > 1) https://lkml.org/lkml/2015/9/15/33
> > > 2) https://lkml.org/lkml/2015/9/21/2
> > 
> > Could you please stop perverting the facts, I did answer to that:
> > https://lkml.org/lkml/2015/9/21/753.
> > 
> > Apart from that, an opinion is not necessarily something I would
> > answer. Concerns about zsmalloc are not in the scope of this patch's
> > discussion. If you have any concerns regarding this particular patch,
> > please let us know.
> 
> Yes, I don't want to interrupt zbud thing which is Seth should maintain
> and I respect his decision but the reason I nacked is you said this patch
> aims for supporing zbud into zsmalloc for determinism.
                               zram

Sorry for the typo.
                

  reply	other threads:[~2015-09-25  8:50 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-22 12:17 [PATCH v2] zbud: allow up to PAGE_SIZE allocations Vitaly Wool
2015-09-22 12:17 ` Vitaly Wool
2015-09-22 21:49 ` Dan Streetman
2015-09-22 21:49   ` Dan Streetman
2015-09-23  8:07   ` Vitaly Wool
2015-09-23  8:07     ` Vitaly Wool
2015-09-23 20:59   ` Vitaly Wool
2015-09-23 20:59     ` Vitaly Wool
2015-09-23 22:41     ` Seth Jennings
2015-09-23 22:41       ` Seth Jennings
2015-09-25  5:56       ` Vitaly Wool
2015-09-25  5:56         ` Vitaly Wool
2015-09-23  3:18 ` Seth Jennings
2015-09-23  3:18   ` Seth Jennings
2015-09-23  7:54   ` Vitaly Wool
2015-09-23  7:54     ` Vitaly Wool
2015-09-23 21:57     ` Seth Jennings
2015-09-23 21:57       ` Seth Jennings
2015-09-25  2:13       ` Minchan Kim
2015-09-25  2:13         ` Minchan Kim
2015-09-25  8:05         ` Sergey Senozhatsky
2015-09-25  8:05           ` Sergey Senozhatsky
2015-09-25  8:27           ` Vitaly Wool
2015-09-25  8:27             ` Vitaly Wool
2015-09-25  9:57             ` Sergey Senozhatsky
2015-09-25  9:57               ` Sergey Senozhatsky
2015-09-25  8:17         ` Vitaly Wool
2015-09-25  8:17           ` Vitaly Wool
2015-09-25  8:47           ` Minchan Kim
2015-09-25  8:47             ` Minchan Kim
2015-09-25  8:50             ` Minchan Kim [this message]
2015-09-25  8:50               ` Minchan Kim
2015-09-25 10:51             ` Vitaly Wool
2015-09-25 10:51               ` Vitaly Wool

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=20150925085002.GA17075@blaptop \
    --to=minchan@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=ddstreet@ieee.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=sjennings@variantweb.net \
    --cc=vitalywool@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.