From: Jens Axboe <[email protected]>
To: Chenliang Li <[email protected]>, [email protected]
Cc: [email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected]
Subject: Re: [PATCH] io_uring/rsrc: Add support for multi-folio buffer coalescing
Date: Mon, 6 May 2024 06:57:44 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 5/6/24 1:53 AM, Chenliang Li wrote:
> Currently fixed buffers consisting of pages in one same folio(huge page)
> can be coalesced into a single bvec entry at registration.
> This patch expands it to support coalescing fixed buffers
> with multiple folios, by:
> 1. Add a helper function and a helper struct to do the coalescing work
> at buffer registration;
> 2. Add the bvec setup procedure of the coalsced path;
coalesced
> 3. store page_mask and page_shift into io_mapped_ubuf for
> later use in io_import_fixed.
Can you add some justification to this commit message? A good commit
message should basically be the WHY of why this commit exists in the
first place. Your commit message just explains what the patch does,
which I can just read the code to see for myself.
As it stands, it's not clear to me or anyone casually reading this
commit message why the change is being done in the first place.
Outside of that, you probably want to split this into two parts - one
that adds the helper for the existing code, then one that modifies it
for your change. We need this to be as simple as possible to review, as
we've had a security issue with page coalescing in this code in the
past.
Minor comments below, will wait with a full review until this is split
to be more easily reviewable.
> +/*
> + * For coalesce to work, a buffer must be one or multiple
> + * folios, all the folios except the first and last one
> + * should be of the same size.
> + */
> +static bool io_sqe_buffer_try_coalesce(struct page **pages,
> + unsigned int nr_pages,
> + struct io_imu_folio_stats *stats)
> +{
> + struct folio *folio = NULL, *first_folio = NULL;
> + unsigned int page_cnt;
> + int i, j;
Please don't make up your own style, follow the style that's already in
the file to begin with.
> diff --git a/io_uring/rsrc.h b/io_uring/rsrc.h
> index c032ca3436ca..4c655e446150 100644
> --- a/io_uring/rsrc.h
> +++ b/io_uring/rsrc.h
> @@ -47,9 +47,18 @@ struct io_mapped_ubuf {
> u64 ubuf_end;
> unsigned int nr_bvecs;
> unsigned long acct_pages;
> + unsigned int page_shift;
> + unsigned long page_mask;
> struct bio_vec bvec[] __counted_by(nr_bvecs);
> };
When adding members to a struct, please be cognizant of how it packs.
I'd suggest making the above:
u64 ubuf_end;
unsigned int nr_bvecs;
unsigned int page_shift;
unsigned long page_mask;
unsigned long acct_pages;
struct bio_vec bvec[] __counted_by(nr_bvecs);
which should pack much nicer and actually save memory.
--
Jens Axboe
next prev parent reply other threads:[~2024-05-06 12:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240506075314epcas5p25333b80c8d6a3217d5352a5a7ed89278@epcas5p2.samsung.com>
2024-05-06 7:53 ` [PATCH] io_uring/rsrc: Add support for multi-folio buffer coalescing Chenliang Li
2024-05-06 12:57 ` Jens Axboe [this message]
[not found] ` <CGME20240507052214epcas5p351e1ff563e3d62bf1fff305dccc1905c@epcas5p3.samsung.com>
2024-05-07 5:22 ` Chenliang Li
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[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