From: Jens Axboe <[email protected]>
To: [email protected], Chenliang Li <[email protected]>
Cc: [email protected], [email protected]
Subject: Re: [PATCH liburing] test/fixed-hugepage: Add small-huge page mixture testcase
Date: Wed, 07 Aug 2024 20:30:17 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Mon, 05 Aug 2024 16:44:42 +0800, Chenliang Li wrote:
> Add a test case where a fixed buffer is composed of a small page and
> a huge page, and begins with the small page. Originally we have huge-small
> test case where the buffer begins with the huge page, add this one to
> cover more should-not-coalesce scenarios.
>
>
Applied, thanks!
[1/1] test/fixed-hugepage: Add small-huge page mixture testcase
commit: 4f134cc45955cf9957e3de9e5f0dbf2162aa49a1
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2024-08-08 2:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240805084453epcas5p363b93b10eaf53df5725417d3d7fbcca0@epcas5p3.samsung.com>
2024-08-05 8:44 ` [PATCH liburing] test/fixed-hugepage: Add small-huge page mixture testcase Chenliang Li
2024-08-08 2:30 ` Jens Axboe [this message]
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=172308421706.296149.16208843385494617309.b4-ty@kernel.dk \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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