netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shannon Nelson <snelson@pensando.io>
To: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org
Cc: drivers@pensando.io, Shannon Nelson <snelson@pensando.io>
Subject: [PATCH net-next 0/4] ionic Tx updates
Date: Mon, 15 Mar 2021 19:31:32 -0700	[thread overview]
Message-ID: <20210316023136.22702-1-snelson@pensando.io> (raw)

Just as the Rx path recently got a face lift, it is time for the Tx path to
get some attention.  The original TSO-to-descriptor mapping was ugly and
convoluted and needed some deep work.  This series pulls the dma mapping
out of the descriptor frag mapping loop and makes the dma mapping more
generic for use in the non-TSO case.

Shannon Nelson (4):
  ionic: simplify TSO descriptor mapping
  ionic: generic tx skb mapping
  ionic: simplify tx clean
  ionic: aggregate Tx byte counting calls

 .../net/ethernet/pensando/ionic/ionic_dev.h   |   6 +-
 .../net/ethernet/pensando/ionic/ionic_txrx.c  | 374 +++++++++---------
 2 files changed, 186 insertions(+), 194 deletions(-)

-- 
2.17.1


             reply	other threads:[~2021-03-16  2:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16  2:31 Shannon Nelson [this message]
2021-03-16  2:31 ` [PATCH net-next 1/4] ionic: simplify TSO descriptor mapping Shannon Nelson
2021-03-16  2:31 ` [PATCH net-next 2/4] ionic: generic tx skb mapping Shannon Nelson
2021-03-16  2:31 ` [PATCH net-next 3/4] ionic: simplify tx clean Shannon Nelson
2021-03-16  2:31 ` [PATCH net-next 4/4] ionic: aggregate Tx byte counting calls Shannon Nelson
2021-03-16 18:20 ` [PATCH net-next 0/4] ionic Tx 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=20210316023136.22702-1-snelson@pensando.io \
    --to=snelson@pensando.io \
    --cc=davem@davemloft.net \
    --cc=drivers@pensando.io \
    --cc=kuba@kernel.org \
    --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).