From: David Laight <david.laight.linux@gmail.com>
To: Caleb Sander Mateos <csander@purestorage.com>
Cc: Jens Axboe <axboe@kernel.dk>, Keith Busch <kbusch@kernel.org>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] block/merge: remove unnecessary min() with UINT_MAX
Date: Sat, 15 Feb 2025 11:51:44 +0000 [thread overview]
Message-ID: <20250215115144.6a10dad8@pumpkin> (raw)
In-Reply-To: <20250214193637.234702-1-csander@purestorage.com>
On Fri, 14 Feb 2025 12:36:36 -0700
Caleb Sander Mateos <csander@purestorage.com> wrote:
> In bvec_split_segs(), max_bytes is an unsigned, so it must be less than
> or equal to UINT_MAX. Remove the unnecessary min().
>
> Prior to commit 67927d220150 ("block/merge: count bytes instead of
> sectors"), the min() was with UINT_MAX >> 9, so it did have an effect.
>
> Signed-off-by: Caleb Sander Mateos <csander@purestorage.com>
> ---
> block/blk-merge.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/block/blk-merge.c b/block/blk-merge.c
> index 15cd231d560c..39b738c0e4c9 100644
> --- a/block/blk-merge.c
> +++ b/block/blk-merge.c
> @@ -268,11 +268,11 @@ static inline unsigned get_max_segment_size(const struct queue_limits *lim,
> */
> static bool bvec_split_segs(const struct queue_limits *lim,
> const struct bio_vec *bv, unsigned *nsegs, unsigned *bytes,
> unsigned max_segs, unsigned max_bytes)
> {
> - unsigned max_len = min(max_bytes, UINT_MAX) - *bytes;
> + unsigned max_len = max_bytes - *bytes;
More interestingly, what stops *bytes being larger than max_bytes?
David
> unsigned len = min(bv->bv_len, max_len);
> unsigned total_len = 0;
> unsigned seg_size = 0;
>
> while (len && *nsegs < max_segs) {
next prev parent reply other threads:[~2025-02-15 11:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 19:36 [PATCH] block/merge: remove unnecessary min() with UINT_MAX Caleb Sander Mateos
2025-02-14 22:40 ` Jens Axboe
2025-02-15 7:33 ` John Garry
2025-02-15 11:51 ` David Laight [this message]
2025-02-16 22:09 ` Caleb Sander Mateos
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=20250215115144.6a10dad8@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.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