From: sashiko-bot@kernel.org
To: "Tariq Toukan" <tariqt@nvidia.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next 2/3] net/mlx5: add frag buf pools create/destroy paths
Date: Fri, 30 Oct 2026 04:53:40 +0000 [thread overview]
Message-ID: <sashiko-outbox-190335@kernel.org> (raw)
In-Reply-To: <20260428052920.219201-3-tariqt@nvidia.com>
> From: Nimrod Oren <noren@nvidia.com>
>
> Introduce mlx5 DMA pool and pool-page data structures, and add the
> creation and teardown paths.
>
> Each NUMA node owns a set of mlx5_dma_pool instances, each one with a
> different block size. The sizes are defined as all powers of two
> starting from MLX5_ADAPTER_PAGE_SHIFT and up to PAGE_SHIFT. Since
> mlx5_frag_bufs are used to back objects whose sizes are encoded relative
> to MLX5_ADAPTER_PAGE_SHIFT, a smaller block_shift value cannot be used.
> Requests larger than PAGE_SIZE continue to be handled as page-sized
> fragments, as in the existing frag-buf allocation model.
>
> Signed-off-by: Nimrod Oren <noren@nvidia.com>
> Signed-off-by: Tariq Toukan <tariqt@nvidia.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260428052920.219201-1-tariqt@nvidia.com?part=2
next prev parent reply other threads:[~2026-10-30 4:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 5:29 [PATCH net-next 0/3] net/mlx5: enable sub-page allocations for mlx5_frag_buf Tariq Toukan
2026-04-28 5:29 ` [PATCH net-next 1/3] net/mlx5: wire frag buf pools lifecycle hooks Tariq Toukan
2026-10-30 4:53 ` sashiko-bot
2026-04-28 5:29 ` [PATCH net-next 2/3] net/mlx5: add frag buf pools create/destroy paths Tariq Toukan
2026-10-30 4:53 ` sashiko-bot [this message]
2026-04-28 5:29 ` [PATCH net-next 3/3] net/mlx5: use internal dma pools for frag buf alloc Tariq Toukan
2026-04-28 14:47 ` 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=sashiko-outbox-190335@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=tariqt@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