From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Vitaly Wool <vitaly.wool@konsulko.se>
Cc: Yosry Ahmed <yosry.ahmed@linux.dev>,
linux-mm@kvack.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, Nhat Pham <nphamcs@gmail.com>,
Shakeel Butt <shakeel.butt@linux.dev>,
Johannes Weiner <hannes@cmpxchg.org>,
Igor Belousov <igor.b@beldev.am>,
Minchan Kim <minchan@kernel.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: Re: [PATCH v4] mm: add zblock allocator
Date: Fri, 2 May 2025 08:49:08 +0900 [thread overview]
Message-ID: <gullx3kk2dogzyxopmvtrhuv5ymfsjbn5mvtwskqkjjfjinqij@s6mmdq2mfwzs> (raw)
In-Reply-To: <e764d05a-6a83-4563-9f28-3f1a3e28727b@konsulko.se>
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?
next prev parent reply other threads:[~2025-05-01 23:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-12 15:42 Vitaly Wool
2025-04-12 19:25 ` Igor Belousov
2025-04-16 12:09 ` Johannes Weiner
2025-04-16 20:10 ` Vitaly
2025-04-17 14:16 ` Johannes Weiner
2025-04-18 7:43 ` Vitaly Wool
2025-04-18 10:52 ` David Hildenbrand
2025-04-18 10:56 ` Vitaly Wool
2025-04-18 11:03 ` David Hildenbrand
2025-04-22 10:46 ` Yosry Ahmed
2025-04-23 19:53 ` Vitaly Wool
2025-04-30 12:27 ` Yosry Ahmed
2025-05-01 12:41 ` Vitaly Wool
2025-05-01 23:43 ` Sergey Senozhatsky
2025-05-06 13:04 ` Yosry Ahmed
2025-06-11 17:11 ` Vitaly Wool
2025-05-01 23:49 ` Sergey Senozhatsky [this message]
2025-05-03 8:27 ` Vitaly
2025-05-04 9:26 ` Andrew Morton
2025-07-20 2:56 ` Andrew Morton
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=gullx3kk2dogzyxopmvtrhuv5ymfsjbn5mvtwskqkjjfjinqij@s6mmdq2mfwzs \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=igor.b@beldev.am \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=nphamcs@gmail.com \
--cc=shakeel.butt@linux.dev \
--cc=vitaly.wool@konsulko.se \
--cc=yosry.ahmed@linux.dev \
/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