public inbox for linux-kselftest@vger.kernel.org
 help / color / mirror / Atom feed
From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Zi Yan <ziy@nvidia.com>,
	linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
	"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
	"Matthew Wilcox (Oracle)" <willy@infradead.org>
Cc: Ryan Roberts <ryan.roberts@arm.com>,
	Hugh Dickins <hughd@google.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>,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 02/10] mm/huge_memory: allow split shmem large folio to any lower order
Date: Wed, 22 Jan 2025 14:44:00 +0800	[thread overview]
Message-ID: <f576f169-24c7-4e53-b5f1-765c10d45e6a@linux.alibaba.com> (raw)
In-Reply-To: <20250116211042.741543-3-ziy@nvidia.com>



On 2025/1/17 05:10, Zi Yan wrote:
> Commit 4d684b5f92ba ("mm: shmem: add large folio support for tmpfs") has
> added large folio support to shmem. Remove the restriction in
> split_huge_page*().

Agree.

> Signed-off-by: Zi Yan <ziy@nvidia.com>

LGTM. Thanks.
Reviewed-by: Baolin Wang <baolin.wang@linux.alibaba.com>

  reply	other threads:[~2025-01-22  6:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-16 21:10 [PATCH v5 00/10] Buddy allocator like folio split Zi Yan
2025-01-16 21:10 ` [PATCH v5 01/10] selftests/mm: make file-backed THP split work by setting force option Zi Yan
2025-01-22  6:32   ` Baolin Wang
2025-01-22 12:21     ` Zi Yan
2025-01-16 21:10 ` [PATCH v5 02/10] mm/huge_memory: allow split shmem large folio to any lower order Zi Yan
2025-01-22  6:44   ` Baolin Wang [this message]
2025-01-16 21:10 ` [PATCH v5 03/10] selftests/mm: test splitting file-backed THP " Zi Yan
2025-01-22  6:47   ` Baolin Wang
2025-01-16 21:10 ` [PATCH v5 04/10] mm/huge_memory: add two new (not yet used) functions for folio_split() Zi Yan
2025-01-16 21:10 ` [PATCH v5 05/10] mm/huge_memory: move folio split common code to __folio_split() Zi Yan
2025-01-16 21:10 ` [PATCH v5 06/10] mm/huge_memory: add buddy allocator like folio_split() Zi Yan
2025-01-16 21:10 ` [PATCH v5 07/10] mm/huge_memory: remove the old, unused __split_huge_page() Zi Yan
2025-01-16 21:10 ` [PATCH v5 08/10] mm/huge_memory: add folio_split() to debugfs testing interface Zi Yan
2025-01-16 21:10 ` [PATCH v5 09/10] mm/truncate: use folio_split() for truncate operation Zi Yan
2025-01-16 21:10 ` [PATCH v5 10/10] 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=f576f169-24c7-4e53-b5f1-765c10d45e6a@linux.alibaba.com \
    --to=baolin.wang@linux.alibaba.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=hughd@google.com \
    --cc=jhubbard@nvidia.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=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