From: Michael Chan <michael.chan@broadcom.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com, gospo@broadcom.com, pavan.chebbi@broadcom.com
Subject: [PATCH net-next 0/3] bnxt_en: Updates
Date: Sun, 6 Nov 2022 19:16:29 -0500 [thread overview]
Message-ID: <1667780192-3700-1-git-send-email-michael.chan@broadcom.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 777 bytes --]
This small patchset adds an improvement to the configuration of ethtool
RSS tuple hash and a PTP improvement when running in a multi-host
environment.
Edwin Peer (2):
bnxt_en: refactor VNIC RSS update functions
bnxt_en: update RSS config using difference algorithm
Pavan Chebbi (1):
bnxt_en: Add a non-real time mode to access NIC clock
drivers/net/ethernet/broadcom/bnxt/bnxt.c | 72 ++++++++++++++-----
drivers/net/ethernet/broadcom/bnxt/bnxt.h | 2 +
.../net/ethernet/broadcom/bnxt/bnxt_ethtool.c | 2 +
drivers/net/ethernet/broadcom/bnxt/bnxt_hsi.h | 47 ++++++++++++
drivers/net/ethernet/broadcom/bnxt/bnxt_ptp.c | 45 ++++++++----
drivers/net/ethernet/broadcom/bnxt/bnxt_ptp.h | 7 +-
6 files changed, 142 insertions(+), 33 deletions(-)
--
2.18.1
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4209 bytes --]
next reply other threads:[~2022-11-07 0:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 0:16 Michael Chan [this message]
2022-11-07 0:16 ` [PATCH net-next 1/3] bnxt_en: refactor VNIC RSS update functions Michael Chan
2022-11-07 7:51 ` Leon Romanovsky
2022-11-07 0:16 ` [PATCH net-next 2/3] bnxt_en: update RSS config using difference algorithm Michael Chan
2022-11-07 7:51 ` Leon Romanovsky
2022-11-07 0:16 ` [PATCH net-next 3/3] bnxt_en: Add a non-real time mode to access NIC clock Michael Chan
2022-11-07 7:51 ` Leon Romanovsky
2022-11-08 11:50 ` [PATCH net-next 0/3] bnxt_en: Updates patchwork-bot+netdevbpf
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=1667780192-3700-1-git-send-email-michael.chan@broadcom.com \
--to=michael.chan@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gospo@broadcom.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.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).