From: Chenliang Li <cliang01.li@samsung.com>
To: cliang01.li@samsung.com
Cc: anuj20.g@samsung.com, asml.silence@gmail.com, axboe@kernel.dk,
gost.dev@samsung.com, io-uring@vger.kernel.org,
joshi.k@samsung.com, kundan.kumar@samsung.com,
peiwei.li@samsung.com
Subject: Re: [Patch v7 0/2] io_uring/rsrc: coalescing multi-hugepage registered buffers
Date: Tue, 23 Jul 2024 15:03:36 +0800 [thread overview]
Message-ID: <20240723070336.2424-1-cliang01.li@samsung.com> (raw)
In-Reply-To: <20240723055616.2362-1-cliang01.li@samsung.com>
On Tue, 23 Jul 2024 13:56:14 +0800, Chenliang Li wrote:
> Changes since v5:
> - Reshuffle the patchset to avoid unused funtion warnings.
> - Store head page of the folio and use folio offset to get rid of
> branching on bvec setups.
> - Add restrictions for non border-aligned folios.
> - Remove unnecessary folio_size field in io_imu_folio_data struct.
>
> v5 : https://lore.kernel.org/io-uring/20240708021426.2217-1-cliang01.li@samsung.com/T/#t
Forgot to add:
Changes since v6:
- Remove the restriction on non-border-aligned single hugepage.
- Code style issue.
v6 : https://lore.kernel.org/io-uring/20240716060807.2707-1-cliang01.li@samsung.com/T/#t
Thanks,
Chenliang Li
next prev parent reply other threads:[~2024-07-23 9:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240723055622epcas5p119f4befb453407a7ac756c1cee582ced@epcas5p1.samsung.com>
2024-07-23 5:56 ` [Patch v7 0/2] io_uring/rsrc: coalescing multi-hugepage registered buffers Chenliang Li
2024-07-23 5:56 ` [Patch v7 1/2] io_uring/rsrc: store folio shift and mask into imu Chenliang Li
2024-07-23 5:56 ` [Patch v7 2/2] io_uring/rsrc: enable multi-hugepage buffer coalescing Chenliang Li
2024-07-23 7:03 ` Chenliang Li [this message]
2024-07-30 11:56 ` [Patch v7 0/2] io_uring/rsrc: coalescing multi-hugepage registered buffers Pavel Begunkov
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=20240723070336.2424-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