linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Minchan Kim <minchan@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: [PATCH 0/2] zsmalloc: fine-grained fullness grouping
Date: Mon,  6 Feb 2023 18:25:57 +0900	[thread overview]
Message-ID: <20230206092559.2722946-1-senozhatsky@chromium.org> (raw)

	Hi,

	zsmalloc has only two fullness group to choose pages from during
zs_malloc() and zs_compact():
- ALMOST_EMPTY for pages with usage ratio equal or less to 3/4 of total
  page capacity
- ALMOST_FULL for pages with usage raio greater than 3/4 of total page
  capacity

This leads to suboptimal page selection for both zs_malloc() and
zs_compact().

This patchset reworks zsmalloc fullness grouping/classification.

Sergey Senozhatsky (2):
  zsmalloc: remove insert_zspage() ->inuse optimization
  zsmalloc: fine-grained inuse ratio based fullness grouping

 mm/zsmalloc.c | 253 +++++++++++++++++++++++++++++++-------------------
 1 file changed, 156 insertions(+), 97 deletions(-)

-- 
2.39.1.519.gcb327c4b5f-goog



             reply	other threads:[~2023-02-06  9:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06  9:25 Sergey Senozhatsky [this message]
2023-02-06  9:25 ` [PATCH 1/2] zsmalloc: remove insert_zspage() ->inuse optimization Sergey Senozhatsky
2023-02-06  9:25 ` [PATCH 2/2] zsmalloc: fine-grained inuse ratio based fullness grouping Sergey Senozhatsky
2023-02-07  1:02   ` Yosry Ahmed
2023-02-07  1:47     ` Sergey Senozhatsky
2023-02-10  4:24       ` Sergey Senozhatsky
2023-02-10  4:25         ` Yosry Ahmed
2023-02-10  4:29           ` Sergey Senozhatsky
2023-02-10  5:15             ` Yosry Ahmed
2023-02-10  5:47               ` Sergey Senozhatsky
2023-02-10  5:52               ` Sergey Senozhatsky
2023-02-10  6:04                 ` Yosry Ahmed
2023-02-10  6:07                   ` 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=20230206092559.2722946-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 \
    /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