From: "David Hildenbrand (Arm)" <david@kernel.org>
To: xu.xin16@zte.com.cn, tujinjiang@huawei.com,
akpm@linux-foundation.org, liam@infradead.org, surenb@google.com,
rppt@kernel.org, ziy@nvidia.com, baolin.wang@linux.alibaba.com,
nico.pache@linux.dev, dev.jain@arm.com, baohua@kernel.org,
lance.yang@linux.dev, chengming.zhou@linux.dev,
usama.arif@linux.dev, gourry@gourry.net, harry@kernel.org,
vbabka@kernel.org, peterz@infradead.org,
borntraeger@linux.ibm.com
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 0/4] mm/ksm: use per-VMA locking for find_mergeable_vma()
Date: Thu, 17 Sep 2026 11:59:47 +0200 [thread overview]
Message-ID: <276ab9d5-74b7-48bf-9cd5-94de0190f221@kernel.org> (raw)
In-Reply-To: <20260913121716693wiN5osmShywgtitghSm7G@zte.com.cn>
On 9/13/26 06:17, xu.xin16@zte.com.cn wrote:
>>> Patch 1 removes an unused 'vma' member from struct folio_walk. It has
>>> never been used since its introduction and is pure cleanup.
I am trying to figure out why your replies don't show up as properly threaded in my inbox, making the discussion impossible to follow.
Looking into your mail:
https://lore.kernel.org/all/20260913121716693wiN5osmShywgtitghSm7G@zte.com.cn/raw
Message-ID: <20260913121716693wiN5osmShywgtitghSm7G@zte.com.cn>
In-Reply-To: <40c0c081-d636-407b-898e-f40f3d5d38cb@huawei.com>
References: 20260911160421076_KNXun8Mpp9Xj7fxHG0i7@zte.com.cn,40c0c081-d636-407b-898e-f40f3d5d38cb@huawei.com
Something is messed up there in the References: tag.
It should be
References: <20260911160421076_KNXun8Mpp9Xj7fxHG0i7@zte.com.cn> <40c0c081-d636-407b-898e-f40f3d5d38cb@huawei.com>
--
Cheers,
David
next prev parent reply other threads:[~2026-09-17 9:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 8:04 [PATCH 0/4] mm/ksm: use per-VMA locking for find_mergeable_vma() xu.xin16
2026-09-11 8:07 ` [PATCH 1/4] mm/pagewalk: delete the unused member xu.xin16
2026-09-11 8:56 ` Lorenzo Stoakes (ARM)
2026-09-11 9:07 ` xu.xin16
2026-09-11 8:09 ` [PATCH 2/4] mm: make folio_walk_start()'s locking asserts scalable xu.xin16
2026-09-11 9:14 ` xu.xin16
2026-09-11 8:12 ` [PATCH 3/4] mm/ksm: make break_ksm() more scalable xu.xin16
2026-09-11 9:04 ` Lorenzo Stoakes (ARM)
2026-09-13 4:42 ` Matthew Wilcox
2026-09-11 8:13 ` [PATCH 4/4] mm/ksm: add find_mergeable_vma_locked() to use per-VMA locking xu.xin16
2026-09-11 8:22 ` Test Case Code " xu.xin16
2026-09-11 9:12 ` xu.xin16
2026-09-14 2:09 ` Longlong Xia
2026-09-14 2:38 ` xu.xin16
2026-09-11 8:47 ` [PATCH 0/4] mm/ksm: use per-VMA locking for find_mergeable_vma() Jinjiang Tu
2026-09-13 4:17 ` xu.xin16
2026-09-14 3:03 ` Jinjiang Tu
2026-09-14 3:09 ` Jinjiang Tu
2026-09-24 3:40 ` xu.xin16
2026-09-17 9:59 ` David Hildenbrand (Arm) [this message]
2026-09-12 8:24 ` [PATCH RFC 0/3] mm/ksm: scan with per-VMA locks Longlong Xia
2026-09-12 8:24 ` [PATCH RFC 1/3] mm/pagewalk: allow folio_walk_start() under a vma read lock Longlong Xia
2026-09-12 8:24 ` [PATCH RFC 2/3] mm/ksm: use the VMA lock when looking up mergeable pages Longlong Xia
2026-09-12 8:24 ` [PATCH RFC 3/3] mm/ksm: scan VMAs with per-VMA locks Longlong Xia
2026-09-13 4:37 ` [PATCH RFC 0/3] mm/ksm: scan " xu.xin16
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=276ab9d5-74b7-48bf-9cd5-94de0190f221@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=borntraeger@linux.ibm.com \
--cc=chengming.zhou@linux.dev \
--cc=dev.jain@arm.com \
--cc=gourry@gourry.net \
--cc=harry@kernel.org \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nico.pache@linux.dev \
--cc=peterz@infradead.org \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=tujinjiang@huawei.com \
--cc=usama.arif@linux.dev \
--cc=vbabka@kernel.org \
--cc=xu.xin16@zte.com.cn \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.