From: Jakub Kicinski <kuba@kernel.org>
To: Taehee Yoo <ap420073@gmail.com>
Cc: davem@davemloft.net, pabeni@redhat.com, edumazet@google.com,
andrew+netdev@lunn.ch, horms@kernel.org,
michael.chan@broadcom.com, pavan.chebbi@broadcom.com,
hawk@kernel.org, ilias.apalodimas@linaro.org,
netdev@vger.kernel.org, dw@davidwei.uk, kuniyu@amazon.com,
sdf@fomichev.me, ahmed.zaki@intel.com,
aleksander.lobakin@intel.com
Subject: Re: [PATCH net-next] eth: bnxt: add support rx side device memory TCP
Date: Tue, 8 Apr 2025 18:59:35 -0700 [thread overview]
Message-ID: <20250408185935.2984648d@kernel.org> (raw)
In-Reply-To: <20250408043545.2179381-1-ap420073@gmail.com>
On Tue, 8 Apr 2025 04:35:45 +0000 Taehee Yoo wrote:
> Currently, bnxt_en driver satisfies the requirements of the Device
> memory TCP, which is HDS.
> So, it implements rx-side Device memory TCP for bnxt_en driver.
> It requires only converting the page API to netmem API.
> `struct page` of agg rings are changed to `netmem_ref netmem` and
> corresponding functions are changed to a variant of netmem API.
>
> It also passes PP_FLAG_ALLOW_UNREADABLE_NETMEM flag to a parameter of
> page_pool.
> The netmem will be activated only when a user requests devmem TCP.
>
> When netmem is activated, received data is unreadable and netmem is
> disabled, received data is readable.
> But drivers don't need to handle both cases because netmem core API will
> handle it properly.
> So, using proper netmem API is enough for drivers.
>
> Device memory TCP can be tested with
> tools/testing/selftests/drivers/net/hw/ncdevmem.
> This is tested with BCM57504-N425G and firmware version 232.0.155.8/pkg
> 232.1.132.8.
drivers/net/ethernet/broadcom/bnxt/bnxt.c:1262:14: warning: variable 'mapping' set but not used [-Wunused-but-set-variable]
1262 | dma_addr_t mapping;
| ^
--
pw-bot: cr
next prev parent reply other threads:[~2025-04-09 1:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 4:35 [PATCH net-next] eth: bnxt: add support rx side device memory TCP Taehee Yoo
2025-04-09 0:35 ` Hongguang Gao
2025-04-09 3:44 ` Hongguang Gao
2025-04-09 3:48 ` Taehee Yoo
2025-04-09 1:59 ` Jakub Kicinski [this message]
2025-04-09 3:49 ` Taehee Yoo
2025-04-09 3:46 ` David Wei
2025-04-10 4:49 ` Mina Almasry
2025-04-10 7:35 ` Taehee Yoo
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=20250408185935.2984648d@kernel.org \
--to=kuba@kernel.org \
--cc=ahmed.zaki@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=ap420073@gmail.com \
--cc=davem@davemloft.net \
--cc=dw@davidwei.uk \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=kuniyu@amazon.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=sdf@fomichev.me \
/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;
as well as URLs for NNTP newsgroup(s).