From: Shannon Nelson <snelson@pensando.io>
To: netdev@vger.kernel.org, davem@davemloft.net
Cc: Shannon Nelson <snelson@pensando.io>
Subject: [PATCH net-next 0/4] ionic txrx updates
Date: Fri, 24 Jul 2020 17:23:22 -0700 [thread overview]
Message-ID: <20200725002326.41407-1-snelson@pensando.io> (raw)
These are a few patches to do some cleanup in the packet
handling and give us more flexibility in tuning performance
by allowing us to put Tx handling on separate interrupts
when it makes sense for particular traffic loads.
Shannon Nelson (4):
ionic: use fewer firmware doorbells on rx fill
ionic: recover from ringsize change failure
ionic: tx separate servicing
ionic: separate interrupt for Tx and Rx
.../ethernet/pensando/ionic/ionic_ethtool.c | 118 +++++++++--
.../net/ethernet/pensando/ionic/ionic_lif.c | 42 +++-
.../net/ethernet/pensando/ionic/ionic_lif.h | 5 +
.../net/ethernet/pensando/ionic/ionic_txrx.c | 188 ++++++++++++------
.../net/ethernet/pensando/ionic/ionic_txrx.h | 2 +
5 files changed, 267 insertions(+), 88 deletions(-)
--
2.17.1
next reply other threads:[~2020-07-25 0:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-25 0:23 Shannon Nelson [this message]
2020-07-25 0:23 ` [PATCH net-next 1/4] ionic: use fewer firmware doorbells on rx fill Shannon Nelson
2020-07-25 0:23 ` [PATCH net-next 2/4] ionic: recover from ringsize change failure Shannon Nelson
2020-07-25 2:44 ` David Miller
2020-07-27 16:42 ` Shannon Nelson
2020-07-25 0:23 ` [PATCH net-next 3/4] ionic: tx separate servicing Shannon Nelson
2020-07-25 0:23 ` [PATCH net-next 4/4] ionic: separate interrupt for Tx and Rx Shannon Nelson
2020-07-25 0:56 ` Jakub Kicinski
2020-07-27 16:37 ` Shannon Nelson
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=20200725002326.41407-1-snelson@pensando.io \
--to=snelson@pensando.io \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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).