From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Nhat Pham <nphamcs@gmail.com>, akpm@linux-foundation.org
Cc: hannes@cmpxchg.org, yosryahmed@google.com, hughd@google.com,
shakeel.butt@linux.dev, ryan.roberts@arm.com,
ying.huang@intel.com, chrisl@kernel.org, david@redhat.com,
kasong@tencent.com, willy@infradead.org, viro@zeniv.linux.org.uk,
baohua@kernel.org, chengming.zhou@linux.dev,
v-songbaohua@oppo.com, linux-mm@kvack.org, kernel-team@meta.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/1] remove SWAP_MAP_SHMEM
Date: Tue, 8 Oct 2024 17:27:35 +0800 [thread overview]
Message-ID: <e1ea6387-eb9e-46b4-a5a8-3f40ad63988e@linux.alibaba.com> (raw)
In-Reply-To: <CAKEwX=Of2U7x+KHikU5p94=qL5VeO_JfysEWKz+=VR3jyq0B5Q@mail.gmail.com>
On 2024/10/2 09:22, Nhat Pham wrote:
> On Tue, Oct 1, 2024 at 6:20 PM Nhat Pham <nphamcs@gmail.com> wrote:
>>
>> Changelog:
>> v2:
>> * Fix a WARN in the shmem THP swap path. Thanks Baolin, Yosry, and Barry
>> for the report and the discussion on how to solve it.
>
> Hi Baolin, could you run your stress program again on this version?
> FWIW, I was able to trigger 64kb mTHP swap in shmem + no-fallback
> swapout, so I think the issue is fixed.
Sure. I'm just back from vacation, and will find some time this week to
test it.
next prev parent reply other threads:[~2024-10-08 9:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 1:20 Nhat Pham
2024-10-02 1:20 ` [PATCH v2 1/1] swap: shmem: " Nhat Pham
2024-10-02 1:33 ` Yosry Ahmed
2024-10-02 1:58 ` Nhat Pham
2024-10-02 2:04 ` Nhat Pham
2024-10-02 2:06 ` Yosry Ahmed
2024-10-02 2:13 ` Yosry Ahmed
2024-10-02 18:01 ` Nhat Pham
2024-10-02 18:06 ` Yosry Ahmed
2024-10-02 2:11 ` Yosry Ahmed
2024-10-11 6:35 ` Huang, Ying
2024-10-11 15:56 ` Nhat Pham
2024-10-02 1:22 ` [PATCH v2 0/1] " Nhat Pham
2024-10-02 1:25 ` Nhat Pham
2024-10-08 9:27 ` Baolin Wang [this message]
2024-10-10 8:53 ` Baolin Wang
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=e1ea6387-eb9e-46b4-a5a8-3f40ad63988e@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=chengming.zhou@linux.dev \
--cc=chrisl@kernel.org \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kasong@tencent.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nphamcs@gmail.com \
--cc=ryan.roberts@arm.com \
--cc=shakeel.butt@linux.dev \
--cc=v-songbaohua@oppo.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=ying.huang@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox