[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMJBoFP5LfoKwzDbSJMmOVOfq=8-7AaoAOV5TVPNt-JcUvZ0eA@mail.gmail.com>
Date: Thu, 17 Sep 2015 12:26:12 +0200
From: Vitaly Wool <vitalywool@...il.com>
To: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
Cc: Dan Streetman <ddstreet@...e.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Minchan Kim <minchan@...nel.org>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
LKML <linux-kernel@...r.kernel.org>, linux-mm@...ck.org
Subject: Re: [PATCH 0/2] prepare zbud to be used by zram as underlying allocator
On Thu, Sep 17, 2015 at 1:30 AM, Sergey Senozhatsky
<sergey.senozhatsky.work@...il.com> wrote:
>
> just a side note,
> I'm afraid this is not how it works. numbers go first, to justify
> the patch set.
>
These patches are extension/alignment patches, why would anyone need
to justify that?
But just to help you understand where I am coming from, here are some numbers:
zsmalloc zbud
kswapd_low_wmark_hit_quickly 4513 5696
kswapd_high_wmark_hit_quickly 861 902
allocstall 2236 1122
pgmigrate_success 78229 31244
compact_stall 1172 634
compact_fail 194 95
compact_success 464 210
These are results from an Android device having run 3 'monkey' tests
each 20 minutes, with user switch to guest and back in between.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists