All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shannon Nelson <shannon.nelson@amd.com>
To: <netdev@vger.kernel.org>, <davem@davemloft.net>, <kuba@kernel.org>
Cc: <drivers@pensando.io>, Shannon Nelson <shannon.nelson@amd.com>
Subject: [PATCH v4 net-next 0/4] ionic: on-chip descriptors
Date: Fri, 10 Feb 2023 16:50:13 -0800	[thread overview]
Message-ID: <20230211005017.48134-1-shannon.nelson@amd.com> (raw)

We start with a couple of house-keeping patches that were originally
presented for 'net', then we add support for on-chip descriptor rings
for tx-push, as well as adding support for rx-push.

I have a patch for the ethtool userland utility that I can send out
once this has been accepted.

v4: added rx-push attributes to ethtool netlink
    converted CMB feature from using a priv-flag to using ethtool tx/rx-push

v3: edited commit message to describe interface-down limitation
    added warn msg if cmb_inuse alloc fails
    removed unnecessary clearing of phy_cmb_pages and cmb_npages
    changed cmb_rings_toggle to use cmb_inuse
    removed unrelated pci_set_drvdata()
    removed unnecessary (u32) cast
    added static inline func for writing CMB descriptors

v2: dropped the rx buffers patch

Shannon Nelson (4):
  ionic: remove unnecessary indirection
  ionic: remove unnecessary void casts
  net: ethtool: extend ringparam set/get APIs for rx_push
  ionic: add tx/rx-push support with device Component Memory Buffers

 Documentation/networking/ethtool-netlink.rst  |   6 +-
 .../ethernet/pensando/ionic/ionic_bus_pci.c   |   6 +-
 .../net/ethernet/pensando/ionic/ionic_dev.c   |  67 +++++++
 .../net/ethernet/pensando/ionic/ionic_dev.h   |  13 ++
 .../ethernet/pensando/ionic/ionic_ethtool.c   | 117 ++++++++++++-
 .../net/ethernet/pensando/ionic/ionic_if.h    |   3 +-
 .../net/ethernet/pensando/ionic/ionic_lif.c   | 165 ++++++++++++++++--
 .../net/ethernet/pensando/ionic/ionic_lif.h   |  40 ++++-
 .../net/ethernet/pensando/ionic/ionic_main.c  |   4 +-
 .../net/ethernet/pensando/ionic/ionic_phc.c   |   2 +-
 .../ethernet/pensando/ionic/ionic_rx_filter.c |   4 +-
 .../net/ethernet/pensando/ionic/ionic_txrx.c  |  22 ++-
 include/linux/ethtool.h                       |   4 +
 include/uapi/linux/ethtool_netlink.h          |   1 +
 net/ethtool/netlink.h                         |   2 +-
 net/ethtool/rings.c                           |  17 +-
 16 files changed, 438 insertions(+), 35 deletions(-)

-- 
2.17.1


             reply	other threads:[~2023-02-11  0:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-11  0:50 Shannon Nelson [this message]
2023-02-11  0:50 ` [PATCH v4 net-next 1/4] ionic: remove unnecessary indirection Shannon Nelson
2023-02-11  0:50 ` [PATCH v4 net-next 2/4] ionic: remove unnecessary void casts Shannon Nelson
2023-02-11  0:50 ` [PATCH v4 net-next 3/4] net: ethtool: extend ringparam set/get APIs for rx_push Shannon Nelson
2023-02-11  0:50 ` [PATCH v4 net-next 4/4] ionic: add tx/rx-push support with device Component Memory Buffers Shannon Nelson
2023-02-11  1:45 ` [PATCH v4 net-next 0/4] ionic: on-chip descriptors Jakub Kicinski
2023-02-13 17:27   ` Shannon Nelson
2023-02-13 11:10 ` 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=20230211005017.48134-1-shannon.nelson@amd.com \
    --to=shannon.nelson@amd.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.