From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH 0/2] bxnt fixes
Date: Tue, 11 Mar 2025 10:11:00 -0700 [thread overview]
Message-ID: <CACZ4nhseSNxteFjmZVFuCVFNaD5ARKayC+5jKUjOqzr1F=8aeg@mail.gmail.com> (raw)
In-Reply-To: <20250310210132.48829-1-ajit.khaparde@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
On Mon, Mar 10, 2025 at 2:01 PM Ajit Khaparde
<ajit.khaparde@broadcom.com> wrote:
>
> These patches address a couple of issues in the BNXT PMD.
> Please apply.
Merged in dpdk-next-net-brcm. Thanks
>
> Ajit Khaparde (2):
> net/bnxt: configure burst threshold based on speed
> net/bnxt: fix epoch bit calculation
>
> drivers/net/bnxt/bnxt_ethdev.c | 20 ++++++++++++++++++++
> drivers/net/bnxt/bnxt_ring.h | 19 +++++++++++++++++++
> drivers/net/bnxt/bnxt_rxq.c | 1 +
> drivers/net/bnxt/bnxt_rxq.h | 2 ++
> drivers/net/bnxt/bnxt_rxr.c | 4 ++++
> drivers/net/bnxt/bnxt_rxtx_vec_avx2.c | 18 ++++++++++--------
> drivers/net/bnxt/bnxt_rxtx_vec_common.h | 11 +++++------
> drivers/net/bnxt/bnxt_rxtx_vec_neon.c | 9 +++++----
> drivers/net/bnxt/bnxt_rxtx_vec_sse.c | 18 ++++++++++--------
> 9 files changed, 76 insertions(+), 26 deletions(-)
>
> --
> 2.39.5 (Apple Git-154)
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4205 bytes --]
prev parent reply other threads:[~2025-03-11 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 21:01 Ajit Khaparde
2025-03-10 21:01 ` [PATCH 1/2] net/bnxt: configure burst threshold based on speed Ajit Khaparde
2025-03-10 21:01 ` [PATCH 2/2] net/bnxt: fix epoch bit calculation Ajit Khaparde
2025-03-11 17:11 ` Ajit Khaparde [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='CACZ4nhseSNxteFjmZVFuCVFNaD5ARKayC+5jKUjOqzr1F=8aeg@mail.gmail.com' \
--to=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).