From: Taehee Yoo <ap420073@gmail.com>
To: Michael Chan <michael.chan@broadcom.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, andrew+netdev@lunn.ch, horms@kernel.org,
pavan.chebbi@broadcom.com, almasrymina@google.com,
praan@google.com, shivajikant@google.com,
asml.silence@gmail.com, sdf@fomichev.me, netdev@vger.kernel.org
Subject: Re: [PATCH v2 net-next] eth: bnxt: add netmem TX support
Date: Thu, 19 Jun 2025 14:06:00 +0900 [thread overview]
Message-ID: <CAMArcTUu3juzMzWUime_ipW4cPiW7Dt_pmgnjfMTgrt18dC4Eg@mail.gmail.com> (raw)
In-Reply-To: <CACKFLik9ZSytqhq8Z=G=ob01J5nDd32JxKcMKrdnxt5R+-gbAQ@mail.gmail.com>
On Thu, Jun 19, 2025 at 2:21 AM Michael Chan <michael.chan@broadcom.com> wrote:
>
Hi Michael,
Thanks a lot for the review :)
> On Wed, Jun 18, 2025 at 6:54 AM Taehee Yoo <ap420073@gmail.com> wrote:
> >
> > Use netmem_dma_*() helpers and declare netmem_tx to support netmem TX.
> > By this change, all bnxt devices will support the netmem TX.
> >
> > Unreadable skbs are not going to be handled by the TX push logic.
> > So, it checks whether a skb is readable or not before the TX push logic.
> >
> > netmem TX can be tested with ncdevmem.c
> >
> > Acked-by: Mina Almasry <almasrymina@google.com>
> > Acked-by: Stanislav Fomichev <sdf@fomichev.me>
> > Signed-off-by: Taehee Yoo <ap420073@gmail.com>
> > ---
> >
> > v2:
> > - Fix commit message.
> > - Add Ack tags from Mina and Stanislav.
> >
>
> Thanks for the patch. At a quick glance, it seems that the netmem dma
> unmap is missing in __bnxt_tx_int().
Thanks! I will change unmaps in __bnxt_in_int() in the v3.
Thanks a lot!
Taehee Yoo
prev parent reply other threads:[~2025-06-19 5:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 13:53 [PATCH v2 net-next] eth: bnxt: add netmem TX support Taehee Yoo
2025-06-18 17:20 ` Michael Chan
2025-06-19 5:06 ` Taehee Yoo [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=CAMArcTUu3juzMzWUime_ipW4cPiW7Dt_pmgnjfMTgrt18dC4Eg@mail.gmail.com \
--to=ap420073@gmail.com \
--cc=almasrymina@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=asml.silence@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=praan@google.com \
--cc=sdf@fomichev.me \
--cc=shivajikant@google.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;
as well as URLs for NNTP newsgroup(s).