From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Andrew Morton <akpm@linux-foundation.org>,
Minchan Kim <minchan@kernel.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: Re: [PATCHv2 0/3] zsmalloc: small compaction improvements
Date: Wed, 5 Jul 2023 22:28:52 +0900 [thread overview]
Message-ID: <20230705132852.GE283328@google.com> (raw)
In-Reply-To: <20230624053120.643409-1-senozhatsky@chromium.org>
On (23/06/24 14:12), Sergey Senozhatsky wrote:
> Hi,
> A tiny series that can reduce the number of
> find_alloced_obj() invocations (which perform a linear
> scan of sub-page) during compaction. Inspired by Alexey
> Romanov's findings.
>
> v2:
> -- picked up a patch from Minchan
>
> Minchan Kim (1):
> zsmalloc: remove zs_compact_control
>
> Sergey Senozhatsky (2):
> zsmalloc: do not scan for allocated objects in empty zspage
> zsmalloc: move migration destination zspage inuse check
Just for the record,
A synthetic zsmalloc fragmentation+compaction test (100% reproducible)
num find_tagged_obj() calls num iterations in find_tagged_obj()
base 545699 812899
patch #1 460701 691821
patch #2 422372 651372
// lower is better
patch #1 is "zsmalloc: do not scan for allocated objects in empty zspage"
patch #2 is "zsmalloc: move migration destination zspage inuse check"
prev parent reply other threads:[~2023-07-05 13:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-24 5:12 Sergey Senozhatsky
2023-06-24 5:12 ` [PATCHv2 1/3] zsmalloc: do not scan for allocated objects in empty zspage Sergey Senozhatsky
2023-06-26 10:57 ` Alexey Romanov
2023-07-01 10:39 ` Sergey Senozhatsky
2023-06-26 17:13 ` Minchan Kim
2023-06-24 5:12 ` [PATCHv2 2/3] zsmalloc: move migration destination zspage inuse check Sergey Senozhatsky
2023-06-26 17:13 ` Minchan Kim
2023-06-24 5:12 ` [PATCHv2 3/3] zsmalloc: remove zs_compact_control Sergey Senozhatsky
2023-06-25 6:10 ` Sergey Senozhatsky
2023-06-26 17:14 ` Minchan Kim
2023-07-01 11:06 ` Sergey Senozhatsky
2023-07-05 13:28 ` Sergey Senozhatsky [this message]
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=20230705132852.GE283328@google.com \
--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