From: Leon Romanovsky <leon@kernel.org>
To: linux-rdma@vger.kernel.org, Jason Gunthorpe <jgg@ziepe.ca>,
Michael Margolin <mrgolin@amazon.com>
Cc: sleybo@amazon.com, matua@amazon.com, gal.pressman@linux.dev,
Firas Jahjah <firasj@amazon.com>,
Yonatan Nachum <ynachum@amazon.com>
Subject: Re: [PATCH for-next] RDMA/core: Fix best page size finding when it can cross SG entries
Date: Fri, 14 Feb 2025 08:57:39 +0200 [thread overview]
Message-ID: <20250214065739.GR17863@unreal> (raw)
In-Reply-To: <173945122413.294504.1292933084740931802.b4-ty@kernel.org>
On Thu, Feb 13, 2025 at 07:53:44AM -0500, Leon Romanovsky wrote:
>
> On Sun, 09 Feb 2025 14:26:08 +0000, Michael Margolin wrote:
> > A single scatter-gather entry is limited by a 32 bits "length" field
> > that is practically 4GB - PAGE_SIZE. This means that even when the
> > memory is physically contiguous, we might need more than one entry to
> > represent it. Additionally when using dmabuf, the sg_table might be
> > originated outside the subsystem and optimized for other needs.
> >
> > For instance an SGT of 16GB GPU continuous memory might look like this:
> > (a real life example)
> >
> > [...]
>
> Applied, thanks!
>
> [1/1] RDMA/core: Fix best page size finding when it can cross SG entries
> https://git.kernel.org/rdma/rdma/c/a4b57de5dfef29
I dropped this patch for now.
Thanks
>
> Best regards,
> --
> Leon Romanovsky <leon@kernel.org>
>
>
prev parent reply other threads:[~2025-02-14 6:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-09 14:26 [PATCH for-next] RDMA/core: Fix best page size finding when it can cross SG entries Michael Margolin
2025-02-13 12:51 ` Leon Romanovsky
2025-02-13 14:04 ` Jason Gunthorpe
2025-02-13 14:30 ` Margolin, Michael
2025-02-13 14:42 ` Jason Gunthorpe
2025-02-13 17:25 ` Margolin, Michael
2025-02-13 17:35 ` Leon Romanovsky
2025-02-13 17:40 ` Jason Gunthorpe
2025-02-13 17:55 ` Leon Romanovsky
2025-02-13 18:12 ` Jason Gunthorpe
2025-02-14 5:55 ` Leon Romanovsky
2025-02-14 15:33 ` Jason Gunthorpe
2025-02-16 8:07 ` Leon Romanovsky
2025-02-17 8:40 ` Margolin, Michael
2025-02-13 12:53 ` Leon Romanovsky
2025-02-14 6:57 ` Leon Romanovsky [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=20250214065739.GR17863@unreal \
--to=leon@kernel.org \
--cc=firasj@amazon.com \
--cc=gal.pressman@linux.dev \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=matua@amazon.com \
--cc=mrgolin@amazon.com \
--cc=sleybo@amazon.com \
--cc=ynachum@amazon.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