linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Chris Li <chrisl@kernel.org>
To: akpm@linux-foundation.org
Cc: linux-mm@kvack.org, kasong@tencent.com, youngjun.park@lge.com,
	 aaron.lu@intel.com, baohua@kernel.org,
	shikemeng@huaweicloud.com,  nphamcs@gmail.com,
	Baoquan He <bhe@redhat.com>
Subject: Re: [PATCH v3 0/2] mm/swapfile.c: select the swap device with default priority round robin
Date: Thu, 9 Oct 2025 19:38:09 -0700	[thread overview]
Message-ID: <CACePvbWRA6NiiKYF=U58VHW_Q1EXBXkun=n4Oa5p16J5y8Qftw@mail.gmail.com> (raw)
In-Reply-To: <aN3vnTumKZTrJvNb@MiWiFi-R3L-srv>

Hi Andrew,

I have reviewed and Ack on both patches in this series.

This series cleans up the per node id complexity and gains about 18%
performance in the constructed test. Please add it to mm-unstable.

Chris

On Wed, Oct 1, 2025 at 8:21 PM Baoquan He <bhe@redhat.com> wrote:
>
> On 09/30/25 at 02:33pm, Baoquan He wrote:
> > Currently, on system with multiple swap devices, swap allocation will
> > select one swap device according to priority. The swap device with the
> > highest priority will be chosen to allocate firstly.
>
> Oops, forgot adding Chris's Suggested-by in this v3 series. The
> Suggested-by tag was added in v1, but I forgot adding it when
> splitting v1 patch into two patches in v3.
>
> I can add it if v4 is needed, or I may need ping Andrew to help add this
> if v3 is OK for merging.
>
> Thanks
> Baoquan
>
>


      reply	other threads:[~2025-10-10  2:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-30  6:33 Baoquan He
2025-09-30  6:33 ` [PATCH v3 1/2] mm/swap: do not choose swap device according to numa node Baoquan He
2025-10-02  2:57   ` Chris Li
2025-10-02 12:38   ` Baoquan He
2025-09-30  6:33 ` [PATCH v3 2/2] mm/swap: select swap device with default priority round robin Baoquan He
2025-10-02  3:03   ` Chris Li
2025-10-02 12:40     ` Baoquan He
2025-10-02 12:39   ` Baoquan He
2025-10-02  3:21 ` [PATCH v3 0/2] mm/swapfile.c: select the " Baoquan He
2025-10-10  2:38   ` Chris Li [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='CACePvbWRA6NiiKYF=U58VHW_Q1EXBXkun=n4Oa5p16J5y8Qftw@mail.gmail.com' \
    --to=chrisl@kernel.org \
    --cc=aaron.lu@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=baohua@kernel.org \
    --cc=bhe@redhat.com \
    --cc=kasong@tencent.com \
    --cc=linux-mm@kvack.org \
    --cc=nphamcs@gmail.com \
    --cc=shikemeng@huaweicloud.com \
    --cc=youngjun.park@lge.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