[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <gullx3kk2dogzyxopmvtrhuv5ymfsjbn5mvtwskqkjjfjinqij@s6mmdq2mfwzs>
Date: Fri, 2 May 2025 08:49:08 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Vitaly Wool <vitaly.wool@...sulko.se>
Cc: Yosry Ahmed <yosry.ahmed@...ux.dev>, linux-mm@...ck.org,
akpm@...ux-foundation.org, linux-kernel@...r.kernel.org, Nhat Pham <nphamcs@...il.com>,
Shakeel Butt <shakeel.butt@...ux.dev>, Johannes Weiner <hannes@...xchg.org>,
Igor Belousov <igor.b@...dev.am>, Minchan Kim <minchan@...nel.org>,
Sergey Senozhatsky <senozhatsky@...omium.org>
Subject: Re: [PATCH v4] mm: add zblock allocator
On (25/04/23 21:53), Vitaly Wool wrote:
[..]
> * zsmalloc/zstd/make -j32 bzImage
> real 8m0.594s
> user 39m37.783s
> sys 8m24.262s
> Zswap: 200600 kB <-- after build completion
> Zswapped: 854072 kB <-- after build completion
> zswpin 309774
> zswpout 1538332
>
> * zblock/zstd/make -j32 bzImage
> real 7m35.546s
> user 38m03.475s
> sys 7m47.407s
> Zswap: 250940 kB <-- after build completion
> Zswapped: 870660 kB <-- after build completion
> zswpin 248606
> zswpout 1277319
I'm sorry but what does this test test? That under memory pressure the
kernel swaps out different pages with different compression characteristics?
Powered by blists - more mailing lists