All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Minchan Kim <minchan@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Yosry Ahmed <yosryahmed@google.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: [PATCHv4 0/4] zsmalloc: fine-grained fullness and new compaction algorithm
Date: Sat,  4 Mar 2023 12:48:31 +0900	[thread overview]
Message-ID: <20230304034835.2082479-1-senozhatsky@chromium.org> (raw)

	Hi,

Existing zsmalloc page fullness grouping leads to suboptimal page
selection for both zs_malloc() and zs_compact(). This patchset
reworks zsmalloc fullness grouping/classification.

Additinally it also implements new compaction algorithm that is
expected to use less CPU-cycles (as it potentially does fewer
memcpy-s in zs_object_copy()).

Test (synthetic) results can be seen in patch 0003.

v4:
-- fixed classes stats loop bug (Yosry)
-- fixed spelling errors (Andrew)
-- dropped some unnecessary hunks from the patches

v3:
-- reworked compaction algorithm implementation (Minchan)
-- keep existing stats and fullness enums (Minchan, Yosry)
-- dropped the patch with new zsmalloc compaction stats (Minchan)
-- report per inuse ratio group classes stats

Sergey Senozhatsky (4):
  zsmalloc: remove insert_zspage() ->inuse optimization
  zsmalloc: fine-grained inuse ratio based fullness grouping
  zsmalloc: rework compaction algorithm
  zsmalloc: show per fullness group class stats

 mm/zsmalloc.c | 358 ++++++++++++++++++++++++--------------------------
 1 file changed, 173 insertions(+), 185 deletions(-)

-- 
2.40.0.rc0.216.gc4246ad0f0-goog


             reply	other threads:[~2023-03-04  3:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-04  3:48 Sergey Senozhatsky [this message]
2023-03-04  3:48 ` [PATCHv4 1/4] zsmalloc: remove insert_zspage() ->inuse optimization Sergey Senozhatsky
2023-03-04  3:48 ` [PATCHv4 2/4] zsmalloc: fine-grained inuse ratio based fullness grouping Sergey Senozhatsky
2023-03-04  3:48 ` [PATCHv4 3/4] zsmalloc: rework compaction algorithm Sergey Senozhatsky
2023-04-17  5:01   ` [PATCH] zsmalloc: reset compaction source zspage pointer after putback_zspage() Sergey Senozhatsky
2023-04-17  5:11     ` Yu Zhao
2023-04-17 11:43     ` Yosry Ahmed
2023-04-17 13:07       ` Sergey Senozhatsky
2023-04-17 13:08   ` Sergey Senozhatsky
2023-03-04  3:48 ` [PATCHv4 4/4] zsmalloc: show per fullness group class stats Sergey Senozhatsky
2023-03-10 21:10 ` [PATCHv4 0/4] zsmalloc: fine-grained fullness and new compaction algorithm Minchan Kim
2023-03-11  8:30   ` Sergey Senozhatsky
2023-04-16  7:20 ` Yu Zhao
2023-04-16 15:18   ` Sergey Senozhatsky
2023-04-16 19:27     ` Yu Zhao
2023-04-17  2:44       ` Sergey Senozhatsky
2023-04-17  2:55         ` Yu Zhao
2023-04-17  3:52           ` Sergey Senozhatsky
2023-04-17  8:29             ` Yosry Ahmed
2023-04-17 11:12               ` Sergey Senozhatsky
2023-04-17 11:16                 ` Yosry Ahmed
2023-04-17 11:24                   ` Sergey Senozhatsky
2023-04-17 11:31                     ` Yosry Ahmed

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=20230304034835.2082479-1-senozhatsky@chromium.org \
    --to=senozhatsky@chromium.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.org \
    --cc=yosryahmed@google.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.