linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Zi Yan <ziy@nvidia.com>
To: "Pankaj Raghav (Samsung)" <kernel@pankajraghav.com>
Cc: Shuah Khan <shuah@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	mcgrof@kernel.org, gost.dev@samsung.com,
	linux-kselftest@vger.kernel.org,
	Pankaj Raghav <p.raghav@samsung.com>
Subject: Re: [PATCH] selftests/mm: do not try to split below filesystem block size
Date: Mon, 26 Aug 2024 10:59:16 -0400	[thread overview]
Message-ID: <340DCD7C-8456-4F5B-B503-9DF5903C16DA@nvidia.com> (raw)
In-Reply-To: <20240826145344.33665-1-kernel@pankajraghav.com>

[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]

On 26 Aug 2024, at 10:53, Pankaj Raghav (Samsung) wrote:

> From: Pankaj Raghav <p.raghav@samsung.com>
>
> There is no point trying to split pagecache thp below the blocksize of
> the filesystem as that is the minimum order that pagecache needs to
> maintain to support blocksizes greater than pagesize [1].

But the purpose of the tests is to make sure all cases are properly handled,
right? If we do not test splitting pagecache large folio below the
block size, we will never know if a kernel change breaks the handling.

Just my two cents.

>
> Set the lower limit for the splitting order to be the fs blocksize
> order.
>
> As the number of tests will now depend on the minimum splitting order,
> move the file preparation before calling ksft_set_plan().
>
> [1] https://lore.kernel.org/linux-fsdevel/20240822135018.1931258-1-kernel@pankajraghav.com/
>
> Signed-off-by: Pankaj Raghav <p.raghav@samsung.com>
> ---
>  .../selftests/mm/split_huge_page_test.c       | 19 +++++++++++++------
>  1 file changed, 13 insertions(+), 6 deletions(-)


--
Best Regards,
Yan, Zi

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 854 bytes --]

  reply	other threads:[~2024-08-26 14:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-26 14:53 Pankaj Raghav (Samsung)
2024-08-26 14:59 ` Zi Yan [this message]
2024-08-26 15:01   ` Pankaj Raghav (Samsung)

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=340DCD7C-8456-4F5B-B503-9DF5903C16DA@nvidia.com \
    --to=ziy@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=gost.dev@samsung.com \
    --cc=kernel@pankajraghav.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mcgrof@kernel.org \
    --cc=p.raghav@samsung.com \
    --cc=shuah@kernel.org \
    /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