Linux io-uring development
 help / color / mirror / Atom feed
From: Chenliang Li <cliang01.li@samsung.com>
To: asml.silence@gmail.com
Cc: anuj20.g@samsung.com, axboe@kernel.dk, cliang01.li@samsung.com,
	gost.dev@samsung.com, io-uring@vger.kernel.org,
	joshi.k@samsung.com, kundan.kumar@samsung.com,
	peiwei.li@samsung.com
Subject: Re: [PATCH liburing v3] test: add test cases for hugepage registered buffers
Date: Thu,  1 Aug 2024 09:01:15 +0800	[thread overview]
Message-ID: <20240801010115.4936-1-cliang01.li@samsung.com> (raw)
In-Reply-To: <2b0e7ae1-ac02-4661-b362-8229cc68abb8@gmail.com>

On Thu, 1 Aug 2024 00:13:10 +0100, Pavel Begunkov wrote:
> On 5/31/24 06:20, Chenliang Li wrote:
>> Add a test file for hugepage registered buffers, to make sure the
>> fixed buffer coalescing feature works safe and soundly.
>> 
>> Testcases include read/write with single/multiple/unaligned/non-2MB
>> hugepage fixed buffers, and also a should-not coalesce case where
>> buffer is a mixture of different size'd pages.
>
> lgtm, would be even better if you can add another patch
> testing adding a small buffer on the left size of a hugepage,
> i.e. like mmap_mixutre() but the small buffer is on the other
> side.

Sure, will add that.

Thanks,
Chenliang Li

  reply	other threads:[~2024-08-01  1:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20240531052031epcas5p3730deb2a19b401e1f772be633b4c6288@epcas5p3.samsung.com>
2024-05-31  5:20 ` [PATCH liburing v3] test: add test cases for hugepage registered buffers Chenliang Li
2024-07-31 23:13   ` Pavel Begunkov
2024-08-01  1:01     ` Chenliang Li [this message]
2024-08-01 20:51       ` Jens Axboe
2024-08-02 10:47         ` Pavel Begunkov
2024-08-02 13:11   ` Jens Axboe

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=20240801010115.4936-1-cliang01.li@samsung.com \
    --to=cliang01.li@samsung.com \
    --cc=anuj20.g@samsung.com \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=gost.dev@samsung.com \
    --cc=io-uring@vger.kernel.org \
    --cc=joshi.k@samsung.com \
    --cc=kundan.kumar@samsung.com \
    --cc=peiwei.li@samsung.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