All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Vitaly Wool <vitalywool@gmail.com>
Cc: ddstreet@ieee.org, akpm@linux-foundation.org, minchan@kernel.org,
	sergey.senozhatsky@gmail.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [PATCH 0/2] prepare zbud to be used by zram as underlying allocator
Date: Thu, 17 Sep 2015 10:30:07 +0900	[thread overview]
Message-ID: <20150917013007.GB421@swordfish> (raw)
In-Reply-To: <20150916134857.e4a71f601a1f68cfa16cb361@gmail.com>

On (09/16/15 13:48), Vitaly Wool wrote:
> as a follow-up to my previous patchset, I decided to first prepare
> zbud/zpool related patches and then have some testing rounds and
> performance measurements for zram running over both, and come up
> with improved/verified zram/zpool patches then.

Hi,

just a side note,
I'm afraid this is not how it works. numbers go first, to justify
the patch set.

	-ss

>
> So for now, here comes the zbud/zpool part.

--
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: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Vitaly Wool <vitalywool@gmail.com>
Cc: ddstreet@ieee.org, akpm@linux-foundation.org, minchan@kernel.org,
	sergey.senozhatsky@gmail.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [PATCH 0/2] prepare zbud to be used by zram as underlying allocator
Date: Thu, 17 Sep 2015 10:30:07 +0900	[thread overview]
Message-ID: <20150917013007.GB421@swordfish> (raw)
In-Reply-To: <20150916134857.e4a71f601a1f68cfa16cb361@gmail.com>

On (09/16/15 13:48), Vitaly Wool wrote:
> as a follow-up to my previous patchset, I decided to first prepare
> zbud/zpool related patches and then have some testing rounds and
> performance measurements for zram running over both, and come up
> with improved/verified zram/zpool patches then.

Hi,

just a side note,
I'm afraid this is not how it works. numbers go first, to justify
the patch set.

	-ss

>
> So for now, here comes the zbud/zpool part.

  parent reply	other threads:[~2015-09-17  1:29 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-16 11:48 [PATCH 0/2] prepare zbud to be used by zram as underlying allocator Vitaly Wool
2015-09-16 11:48 ` Vitaly Wool
2015-09-16 11:50 ` [PATCH 1/2] zbud: allow PAGE_SIZE allocations Vitaly Wool
2015-09-16 11:50   ` Vitaly Wool
2015-09-17 13:00   ` Vlastimil Babka
2015-09-17 13:00     ` Vlastimil Babka
2015-09-18  8:03     ` Vitaly Wool
2015-09-18  8:03       ` Vitaly Wool
2015-09-21 15:27       ` Dan Streetman
2015-09-21 15:27         ` Dan Streetman
2015-09-21 16:17   ` Dan Streetman
2015-09-21 16:17     ` Dan Streetman
2015-09-22 10:18     ` Vitaly Wool
2015-09-22 10:18       ` Vitaly Wool
2015-09-22 17:09       ` Dan Streetman
2015-09-22 17:09         ` Dan Streetman
2015-09-16 11:53 ` [PATCH 2/2] zpool/zsmalloc/zbud: align on interfaces Vitaly Wool
2015-09-16 11:53   ` Vitaly Wool
2015-09-21 17:15   ` Dan Streetman
2015-09-21 17:15     ` Dan Streetman
2015-09-17  1:30 ` Sergey Senozhatsky [this message]
2015-09-17  1:30   ` [PATCH 0/2] prepare zbud to be used by zram as underlying allocator Sergey Senozhatsky
2015-09-17 10:26   ` Vitaly Wool
2015-09-17 10:26     ` Vitaly Wool
2015-09-21  4:18     ` Minchan Kim
2015-09-21  4:18       ` Minchan Kim
2015-09-21 21:11       ` Vitaly Wool
2015-09-21 21:11         ` Vitaly Wool
2015-09-22 15:36         ` Minchan Kim
2015-09-22 15:36           ` Minchan Kim
2015-09-22 16:49           ` Austin S Hemmelgarn

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=20150917013007.GB421@swordfish \
    --to=sergey.senozhatsky.work@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=ddstreet@ieee.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.org \
    --cc=sergey.senozhatsky@gmail.com \
    --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.