From: Yishai Hadas <yishaih@nvidia.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Matthew Wilcox <willy@infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-block@vger.kernel.org>,
<linux-mm@kvack.org>, <axboe@kernel.dk>, <logang@deltatee.com>,
<hch@lst.de>, <alex.williamson@redhat.com>, <leonro@nvidia.com>,
<maorg@nvidia.com>
Subject: Re: [PATCH] lib/scatterlist: Fix to calculate the last_pg properly
Date: Tue, 10 Jan 2023 17:05:06 +0200 [thread overview]
Message-ID: <e4d40ba2-658a-8390-248a-1ca754f320cb@nvidia.com> (raw)
In-Reply-To: <Y71t3yyFvdLXM+qd@nvidia.com>
On 10/01/2023 15:53, Jason Gunthorpe wrote:
> On Tue, Jan 10, 2023 at 10:01:53AM +0200, Yishai Hadas wrote:
>> On 10/01/2023 7:08, Matthew Wilcox wrote:
>>> On Mon, Jan 09, 2023 at 04:47:01PM +0200, Yishai Hadas wrote:
>>>> if (sgt_append->prv) {
>>>> + unsigned long paddr =
>>>> + (page_to_pfn(sg_page(sgt_append->prv)) * PAGE_SIZE +
>>> 1. page_to_pfn() * PAGE_SIZE is spelled page_to_phys()
>>>
>>> 2. physical addresses have type phys_addr_t. Oh, wait, paddr isn't a
>>> physical address, it's a pfn because you divide by PAGE_SIZE at the end.
>>> But you will get truncation on 32-bit, because page_to_pfn() has type
>>> unsigned long. Anyway, this shouldn't be called paddr. Maybe last_pfn
>>> or something?
>>>
>>>> + sgt_append->prv->offset + sgt_append->prv->length) /
>>>> + PAGE_SIZE;
>> In this area of the patch I just reverted to what we had in 6.1 [1] where we
>> were good.
>>
>> I can send V1 and replace the 'paddr' to be called 'last_pfn' if it's really
>> needed.
> Please change it as Matthew describes so it is clearer
>
> Jason
OK
Once cleaning the code and renaming to 'last_pfn', could also see that
we had to use below '- 1' instead of '- PAGE_SIZE'.
The expected diff compared to V0 can be seen below.
Will repeat some testing and send V1 once be ready.
+++ b/lib/scatterlist.c
@@ -470,18 +470,16 @@ int sg_alloc_append_table_from_pages(struct
sg_append_table *sgt_append,
return -EOPNOTSUPP;
if (sgt_append->prv) {
- unsigned long paddr =
- (page_to_pfn(sg_page(sgt_append->prv)) * PAGE_SIZE +
- sgt_append->prv->offset +
sgt_append->prv->length) /
- PAGE_SIZE;
+ unsigned long last_pfn =
(page_to_phys(sg_page(sgt_append->prv)) +
+ sgt_append->prv->offset +
sgt_append->prv->length) / PAGE_SIZE;
if (WARN_ON(offset))
return -EINVAL;
/* Merge contiguous pages into the last SG */
prv_len = sgt_append->prv->length;
- if (page_to_pfn(pages[0]) == paddr) {
- last_pg = pfn_to_page(paddr - PAGE_SIZE);
+ if (page_to_pfn(pages[0]) == last_pfn) {
+ last_pg = pfn_to_page(last_pfn - 1);
while (n_pages && pages_are_mergeable(pages[0],
last_pg)) {
if (sgt_append->prv->length + PAGE_SIZE
> max_segment)
break;
Yishai
prev parent reply other threads:[~2023-01-10 15:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 14:47 Yishai Hadas
2023-01-09 18:08 ` Logan Gunthorpe
2023-01-10 3:18 ` Jens Axboe
2023-01-11 0:03 ` Andrew Morton
2023-01-11 13:28 ` Jason Gunthorpe
2023-01-10 5:08 ` Matthew Wilcox
2023-01-10 8:01 ` Yishai Hadas
2023-01-10 13:53 ` Jason Gunthorpe
2023-01-10 15:05 ` Yishai Hadas [this message]
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=e4d40ba2-658a-8390-248a-1ca754f320cb@nvidia.com \
--to=yishaih@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=jgg@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=logang@deltatee.com \
--cc=maorg@nvidia.com \
--cc=willy@infradead.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