From: Mike Rapoport <rppt@kernel.org>
To: Leon Romanovsky <leon@kernel.org>
Cc: Potnuri Bharat Teja <bharat@chelsio.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Yishai Hadas <yishaih@nvidia.com>,
Nelson Escobar <neescoba@cisco.com>,
Satish Kharat <satishkh@cisco.com>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH rdma-next 0/4] RDMA: use kmalloc() for remaining scratch buffers
Date: Thu, 16 Jul 2026 08:52:28 +0300 [thread overview]
Message-ID: <alhxnOTeJHNmgkrk@kernel.org> (raw)
In-Reply-To: <20260715-get_pages-to-kmalloc-v1-0-b0b7fce288be@nvidia.com>
On Wed, Jul 15, 2026 at 02:03:08PM +0300, Leon Romanovsky wrote:
> The series [PATCH v2 0/5] RDMA, IB: replace __get_free_pages() with
> kmalloc() [1] replaced direct page allocator use in RDMA buffers that
> have no page-specific requirements. Continue that cleanup for the remaining
> scratch buffers in cxgb4, mlx4, usnic and mlx5.
>
> Use kmalloc() or kzalloc() to retain the existing physically contiguous
> storage and alignment while avoiding casts and allowing kfree() to derive
> the allocation size. The mlx5 patch converts every allocation tier in the
> shared UMR buffer allocator so its cleanup path does not mix allocator
> families.
>
> Allocations in qedr, cxgb4 and bnxt_re that back userspace mappings are
> intentionally unchanged. Those buffers are passed to vm_insert_page() or
> io_remap_pfn_range() and must remain individual page allocations rather
> than slab pages.
>
> [1] https://lore.kernel.org/all/20260713-b4-rdma-v2-0-65d2a1a5180c@kernel.org/
>
> Link: https://lore.kernel.org/all/635405e4-9423-4a25-a6e7-e03c8ea0bcbe@redhat.com
> Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
Thanks, Leon!
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-07-16 5:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 11:03 [PATCH rdma-next 0/4] RDMA: use kmalloc() for remaining scratch buffers Leon Romanovsky
2026-07-15 11:03 ` [PATCH rdma-next 1/4] RDMA/cxgb4: use kmalloc() for the PBL address array Leon Romanovsky
2026-07-15 11:03 ` [PATCH rdma-next 2/4] RDMA/mlx4: use kzalloc() for the fast registration page list Leon Romanovsky
2026-07-15 11:03 ` [PATCH rdma-next 3/4] RDMA/usnic: use kmalloc() for the page pointer array Leon Romanovsky
2026-07-15 11:03 ` [PATCH rdma-next 4/4] RDMA/mlx5: use kmalloc() for UMR translation buffers Leon Romanovsky
2026-07-16 5:52 ` Mike Rapoport [this message]
2026-07-16 9:03 ` [PATCH rdma-next 0/4] RDMA: use kmalloc() for remaining scratch buffers Leon Romanovsky
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=alhxnOTeJHNmgkrk@kernel.org \
--to=rppt@kernel.org \
--cc=bharat@chelsio.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=neescoba@cisco.com \
--cc=satishkh@cisco.com \
--cc=yishaih@nvidia.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