mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Ehab Ababneh <ehab.ababneh@intel.com>
Cc: ziy@nvidia.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	 buddy.lumpkin@oracle.com, akpm@linux-foundation.org,
	kasong@tencent.com,  qi.zheng@linux.dev, shakeel.butt@linux.dev,
	baohua@kernel.org,  axelrasmussen@google.com, yuanchu@google.com,
	weixugc@google.com, david@kernel.org,  liam@infradead.org,
	vbabka@kernel.org, rppt@kernel.org, surenb@google.com,
	 mhocko@suse.com, jackmanb@google.com, hannes@cmpxchg.org,
	baoquan.he@linux.dev,  baolin.wang@linux.alibaba.com
Subject: Re: [RFC PATCH v2 0/5] mm/vmscan: adaptive multi-threaded kswapd for NUMA-aware reclaim
Date: Fri, 9 Oct 2026 21:40:00 +0100	[thread overview]
Message-ID: <aslREDvk7gsfkHDl@gremlin> (raw)
In-Reply-To: <cover.1791577417.git.ehab.ababneh@intel.com>

Hi,

Please always send new revisions of series individually, not in-reply-to
any other email.

The easiest way of accomplishing this is to use b4 [0] (the recommended
way of sending patches to mm), otherwise format patches like this:

For a patch series, e.g. at v2:

$ git format-patch -v2 --cover-letter --thread ...

For an individual patch, e.g. at v2:

$ git format-patch -v2 HEAD~1

[0]: https://b4.docs.kernel.org/en/latest/contributor/send.html

--
Cheers, Lorenzo

  parent reply	other threads:[~2026-10-09 20:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08 22:10 [RFC PATCH 0/3] " Ehab Ababneh
2026-09-08 22:10 ` [RFC PATCH 1/3] vmscan: Support multiple kswapd threads per node Ehab Ababneh
2026-09-08 22:10 ` [RFC PATCH 2/3] mm/vmscan: handle racing max_seq advancement Ehab Ababneh
2026-09-08 22:10 ` [RFC PATCH 3/3] mm/vmscan: make kswapd wakeups NUMA load-aware Ehab Ababneh
2026-09-09  2:16 ` [RFC PATCH 0/3] mm/vmscan: adaptive multi-threaded kswapd for NUMA-aware reclaim Zi Yan
2026-09-22 21:23   ` Ababneh, Ehab
2026-10-09 20:32     ` [RFC PATCH v2 0/5] " Ehab Ababneh
2026-10-09 20:33       ` [RFC PATCH v2 1/5] vmscan: Support multiple kswapd threads per node Ehab Ababneh
2026-10-10  8:51         ` Barry Song
2026-10-09 20:33       ` [RFC PATCH v2 2/5] mm/vmscan: silence spurious max_seq race warning Ehab Ababneh
2026-10-09 20:33       ` [RFC PATCH v2 3/5] mm/vmscan: make kswapd wakeups NUMA load-aware Ehab Ababneh
2026-10-09 20:33       ` [RFC PATCH v2 4/5] mm/vmscan: let kswapd scan minimum-generation lruvecs Ehab Ababneh
2026-10-09 20:33       ` [RFC PATCH v2 5/5] mm/vmscan: scale hopeless threshold for kswapd workers Ehab Ababneh
2026-10-09 20:40       ` Lorenzo Stoakes (ARM) [this message]
2026-10-10  8:19       ` [RFC PATCH v2 0/5] mm/vmscan: adaptive multi-threaded kswapd for NUMA-aware reclaim Barry Song

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=aslREDvk7gsfkHDl@gremlin \
    --to=ljs@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=axelrasmussen@google.com \
    --cc=baohua@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=baoquan.he@linux.dev \
    --cc=buddy.lumpkin@oracle.com \
    --cc=david@kernel.org \
    --cc=ehab.ababneh@intel.com \
    --cc=hannes@cmpxchg.org \
    --cc=jackmanb@google.com \
    --cc=kasong@tencent.com \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=qi.zheng@linux.dev \
    --cc=rppt@kernel.org \
    --cc=shakeel.butt@linux.dev \
    --cc=surenb@google.com \
    --cc=vbabka@kernel.org \
    --cc=weixugc@google.com \
    --cc=yuanchu@google.com \
    --cc=ziy@nvidia.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
all inboxes | Powered by JetHome®