From: Andrew Morton <akpm@linux-foundation.org>
To: Chris Li <chrisl@kernel.org>
Cc: Kairui Song <kasong@tencent.com>,
Ryan Roberts <ryan.roberts@arm.com>,
"Huang, Ying" <ying.huang@intel.com>,
Kalesh Singh <kaleshsingh@google.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Barry Song <baohua@kernel.org>
Subject: Re: [PATCH v2 0/2] mm: swap: mTHP swap allocator base on swap cluster order
Date: Fri, 14 Jun 2024 19:59:21 -0700 [thread overview]
Message-ID: <20240614195921.a20f1766a78b27339a2a3128@linux-foundation.org> (raw)
In-Reply-To: <CANeU7Q=Nd3Os7cm-Lu4h5fvkMdoHeYbtjkUja+sAMcJ2moMKrQ@mail.gmail.com>
On Fri, 14 Jun 2024 19:51:11 -0700 Chris Li <chrisl@kernel.org> wrote:
> > I'm having trouble understanding the overall impact of this on users.
> > We fail the mTHP swap allocation and fall back, but things continue to
> > operate OK?
>
> Continue to operate OK in the sense that the mTHP will have to split
> into 4K pages before the swap out, aka the fall back. The swap out and
> swap in can continue to work as 4K pages, not as the mTHP. Due to the
> fallback, the mTHP based zsmalloc compression with 64K buffer will not
> happen. That is the effect of the fallback. But mTHP swap out and swap
> in is relatively new, it is not really a regression.
Sure, but it's pretty bad to merge a new feature only to have it
ineffective after a few hours use.
> >
> > > There is some test number in the V1 thread of this series:
> > > https://lore.kernel.org/r/20240524-swap-allocator-v1-0-47861b423b26@kernel.org
> >
> > Well, please let's get the latest numbers into the latest patchset.
> > Along with a higher-level (and quantitative) description of the user impact.
>
> I will need Barray's help to collect the number. I don't have the
> setup to reproduce his test result.
> Maybe a follow up commit message amendment for the test number when I get it?
Yep, I alter changelogs all the time.
> >
> > I'll add this into mm-unstable now for some exposure, but at this point
> > I'm not able to determine whether it should go in as a hotfix for
> > 6.10-rcX.
>
> Maybe not need to be a hotfix. Not all Barry's mTHP swap out and swap
> in patch got merged yet.
OK, well please let's give appropriate consideration to what we should
add to 6.10-rcX in order to have this feature working well.
next prev parent reply other threads:[~2024-06-15 3:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 23:48 Chris Li
2024-06-14 23:48 ` [PATCH v2 1/2] mm: swap: swap cluster switch to double link list Chris Li
2024-06-17 6:19 ` Huang, Ying
2024-06-18 5:06 ` Chris Li
2024-06-18 7:54 ` Huang, Ying
2024-06-18 10:01 ` Chris Li
2024-06-19 7:51 ` Huang, Ying
2024-06-19 9:03 ` Chris Li
2024-06-14 23:48 ` [PATCH v2 2/2] mm: swap: mTHP allocate swap entries from nonfull list Chris Li
2024-06-15 1:06 ` [PATCH v2 0/2] mm: swap: mTHP swap allocator base on swap cluster order Andrew Morton
2024-06-15 2:51 ` Chris Li
2024-06-15 2:59 ` Andrew Morton [this message]
2024-06-15 8:47 ` Barry Song
2024-06-17 3:00 ` Huang, Ying
2024-06-17 3:12 ` Barry Song
2024-06-17 3:29 ` Barry Song
2024-06-17 6:48 ` Huang, Ying
2024-06-17 7:08 ` Barry Song
2024-06-17 18:34 ` Chris Li
2024-06-17 23:00 ` Hugh Dickins
2024-06-17 23:47 ` Chris Li
2024-06-18 13:08 ` David Hildenbrand
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=20240614195921.a20f1766a78b27339a2a3128@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=chrisl@kernel.org \
--cc=kaleshsingh@google.com \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryan.roberts@arm.com \
--cc=ying.huang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox