From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
"linux-m68k@lists.linux-m68k.org"
<linux-m68k@lists.linux-m68k.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH 2/2] block: pass a phys_addr_t to get_max_segment_size
Date: Sat, 6 Jul 2024 10:37:11 +0000 [thread overview]
Message-ID: <6ae64d5e-bc86-4c4b-bc3a-3d72e86d0dbf@nvidia.com> (raw)
In-Reply-To: <20240706075228.2350978-3-hch@lst.de>
On 7/6/2024 12:52 AM, Christoph Hellwig wrote:
> Work on a single address to simplify the logic, and prepare the callers
> from using better helpers.
>
> Signed-off-by: Christoph Hellwig<hch@lst.de>
> ---
> block/blk-merge.c | 25 +++++++++++--------------
> 1 file changed, 11 insertions(+), 14 deletions(-)
>
> diff --git a/block/blk-merge.c b/block/blk-merge.c
> index cff20bcc0252a7..e41ea331809936 100644
> --- a/block/blk-merge.c
> +++ b/block/blk-merge.c
> @@ -209,23 +209,22 @@ static inline unsigned get_max_io_size(struct bio *bio,
> /**
> * get_max_segment_size() - maximum number of bytes to add as a single segment
> * @lim: Request queue limits.
> - * @start_page: See below.
> - * @offset: Offset from @start_page where to add a segment.
> + * @paddr: address of the range to add
> + * @max_len: maximum length available to add at @paddr
> *
> - * Returns the maximum number of bytes that can be added as a single segment.
> + * Returns the maximum number of bytes of the range starting at @paddr that can
> + * be added to a single segment.
> */
> static inline unsigned get_max_segment_size(const struct queue_limits *lim,
> - struct page *start_page, unsigned long offset)
> + phys_addr_t paddr, unsigned int len)
> {
> - unsigned long mask = lim->seg_boundary_mask;
> -
> - offset = mask & (page_to_phys(start_page) + offset);
> -
> /*
> * Prevent an overflow if mask = ULONG_MAX and offset = 0 by adding 1
> * after having calculated the minimum.
> */
> - return min(mask - offset, (unsigned long)lim->max_segment_size - 1) + 1;
> + return min_t(unsigned long, len,
> + min(lim->seg_boundary_mask - (lim->seg_boundary_mask & paddr),
> + (unsigned long)lim->max_segment_size - 1) + 1);
> }
>
Looks good, is it possible to re-write last
return min_t(..., ..., min(..., ...)) statement something like totally
untested in [1] ?
Irrespective of that, looks good.
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
-ck
[1]
static inline unsigned get_max_segment_size(const struct queue_limits *lim,
phys_addr_t paddr, unsigned int paddr_len)
{
unsigned long paddr_max_seg_allowed_len;
unsigned long paddr_seg_boundry;
paddr_seg_boundry =
lim->seg_boundary_mask - (lim->seg_boundary_mask & paddr);
/*
* Prevent an overflow if mask = ULONG_MAX and offset = 0 by
adding 1
* after having calculated the minimum.
*/
paddr_max_seg_allowed_len = min(paddr_seg_boundry,
(unsigned long)lim->max_segment_size -
1) + 1;
return min_t(unsigned long, paddr_len, paddr_max_seg_allowed_len);
}
next prev parent reply other threads:[~2024-07-06 10:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-06 7:52 add a bvec_phys helper v3 Christoph Hellwig
2024-07-06 7:52 ` [PATCH 1/2] block: add a bvec_phys helper Christoph Hellwig
2024-07-06 9:57 ` Chaitanya Kulkarni
2024-07-06 7:52 ` [PATCH 2/2] block: pass a phys_addr_t to get_max_segment_size Christoph Hellwig
2024-07-06 10:37 ` Chaitanya Kulkarni [this message]
2024-07-07 6:40 ` Christoph Hellwig
2024-07-09 12:39 ` Geert Uytterhoeven
2024-07-10 5:52 ` Christoph Hellwig
2024-07-10 7:08 ` Geert Uytterhoeven
2024-07-08 7:52 ` add a bvec_phys helper v3 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2024-07-05 12:32 add a bvec_phys helper v2 Christoph Hellwig
2024-07-05 12:32 ` [PATCH 2/2] block: pass a phys_addr_t to get_max_segment_size Christoph Hellwig
2024-07-06 6:21 ` Jens Axboe
2024-07-06 6:22 ` Christoph Hellwig
2024-07-06 6:24 ` 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=6ae64d5e-bc86-4c4b-bc3a-3d72e86d0dbf@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=axboe@kernel.dk \
--cc=geert@linux-m68k.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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