From: Andrew Morton <akpm@linux-foundation.org>
To: Zi Yan <ziy@nvidia.com>
Cc: Hugh Dickins <hughd@google.com>,
linux-mm@kvack.org,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Ryan Roberts <ryan.roberts@arm.com>,
David Hildenbrand <david@redhat.com>,
Yang Shi <yang@os.amperecomputing.com>,
Miaohe Lin <linmiaohe@huawei.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Yu Zhao <yuzhao@google.com>, John Hubbard <jhubbard@nvidia.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Kairui Song <kasong@tencent.com>,
Liu Shixin <liushixin2@huawei.com>
Subject: Re: [PATCH v9 2/8] mm/huge_memory: add two new (not yet used) functions for folio_split()
Date: Tue, 4 Mar 2025 12:29:37 -0800 [thread overview]
Message-ID: <20250304122937.069e539c99c3b1b51985c467@linux-foundation.org> (raw)
In-Reply-To: <408B0C17-E144-4729-9461-80E8B5D1360C@nvidia.com>
On Tue, 04 Mar 2025 11:20:53 -0500 Zi Yan <ziy@nvidia.com> wrote:
> Do you mind folding Hugh’s fixes to this patch? Let me know if you prefer
> a V10. Thanks.
I think a new series, please. I'll remove the current version from mm.git.
Can I suggest that you repeat Hugh's testing, hopefully see the same
failures and then get in and debug them?
next prev parent reply other threads:[~2025-03-04 20:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 21:00 [PATCH v9 0/8] Buddy allocator like (or non-uniform) folio split Zi Yan
2025-02-26 21:00 ` [PATCH v9 1/8] xarray: add xas_try_split() to split a multi-index entry Zi Yan
2025-02-26 21:00 ` [PATCH v9 2/8] mm/huge_memory: add two new (not yet used) functions for folio_split() Zi Yan
2025-02-27 5:55 ` Matthew Wilcox
2025-02-27 15:14 ` Matthew Wilcox
2025-02-27 15:42 ` Zi Yan
2025-03-04 11:49 ` Hugh Dickins
2025-03-04 16:20 ` Zi Yan
2025-03-04 20:29 ` Andrew Morton [this message]
2025-03-04 20:34 ` Zi Yan
2025-03-05 21:03 ` Hugh Dickins
2025-03-05 21:10 ` Zi Yan
2025-03-05 22:38 ` Hugh Dickins
2025-03-06 16:21 ` Zi Yan
2025-03-07 15:23 ` Zi Yan
2025-03-10 8:54 ` Hugh Dickins
2025-03-10 15:35 ` Zi Yan
2025-03-05 19:45 ` Zi Yan
2025-03-05 20:50 ` Hugh Dickins
2025-03-05 21:08 ` Zi Yan
2025-03-05 21:49 ` Hugh Dickins
2025-03-06 9:19 ` David Hildenbrand
2025-03-06 16:27 ` Zi Yan
2025-03-07 17:46 ` David Hildenbrand
2025-02-26 21:00 ` [PATCH v9 3/8] mm/huge_memory: move folio split common code to __folio_split() Zi Yan
2025-02-26 21:00 ` [PATCH v9 4/8] mm/huge_memory: add buddy allocator like (non-uniform) folio_split() Zi Yan
2025-02-26 21:00 ` [PATCH v9 5/8] mm/huge_memory: remove the old, unused __split_huge_page() Zi Yan
2025-02-26 21:00 ` [PATCH v9 6/8] mm/huge_memory: add folio_split() to debugfs testing interface Zi Yan
2025-02-26 21:00 ` [PATCH v9 7/8] mm/truncate: use buddy allocator like folio split for truncate operation Zi Yan
2025-03-02 3:52 ` Zi Yan
2025-02-26 21:00 ` [PATCH v9 8/8] selftests/mm: add tests for folio_split(), buddy allocator like split Zi Yan
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=20250304122937.069e539c99c3b1b51985c467@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=hughd@google.com \
--cc=jhubbard@nvidia.com \
--cc=kasong@tencent.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liushixin2@huawei.com \
--cc=ryan.roberts@arm.com \
--cc=wangkefeng.wang@huawei.com \
--cc=willy@infradead.org \
--cc=yang@os.amperecomputing.com \
--cc=yuzhao@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