linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Andrew Morton <akpm@linux-foundation.org>,
	Minchan Kim <minchan@kernel.org>
Cc: Mike Kravetz <mike.kravetz@oracle.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: [PATCHv3 0/4] zsmalloc: make zspage chain size configurable
Date: Wed, 18 Jan 2023 09:52:06 +0900	[thread overview]
Message-ID: <20230118005210.2814763-1-senozhatsky@chromium.org> (raw)

Hi,

	This turns hard coded limit on maximum number of physical
pages per-zspage into a config option. It also increases the default
limit from 4 to 8.

v3:
-- Fixed zspage isolated bitfield overflow (Mike)
-- Fixed parisc64 build failure (0day)
-- Minumum chain size value is 4 now (which has been zsmalloc default
   for ages)
-- Picked up Minchan's Acked-by

Sergey Senozhatsky (4):
  zsmalloc: rework zspage chain size selection
  zsmalloc: skip chain size calculation for pow_of_2 classes
  zsmalloc: make zspage chain size configurable
  zsmalloc: set default zspage chain size to 8

 Documentation/mm/zsmalloc.rst | 168 ++++++++++++++++++++++++++++++++++
 mm/Kconfig                    |  19 ++++
 mm/zsmalloc.c                 |  71 ++++++--------
 3 files changed, 213 insertions(+), 45 deletions(-)

-- 
2.39.0.314.g84b9a713c41-goog



             reply	other threads:[~2023-01-18  0:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18  0:52 Sergey Senozhatsky [this message]
2023-01-18  0:52 ` [PATCHv3 1/4] zsmalloc: rework zspage chain size selection Sergey Senozhatsky
2023-01-18  0:52 ` [PATCHv3 2/4] zsmalloc: skip chain size calculation for pow_of_2 classes Sergey Senozhatsky
2023-01-18  0:52 ` [PATCHv3 3/4] zsmalloc: make zspage chain size configurable Sergey Senozhatsky
2023-01-18  0:52 ` [PATCHv3 4/4] zsmalloc: set default zspage chain size to 8 Sergey Senozhatsky

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=20230118005210.2814763-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=mike.kravetz@oracle.com \
    --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