linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, linux-doc@vger.kernel.org,
	chenhao288@hisilicon.com, huangguangbin2@huawei.com,
	idosch@nvidia.com, corbet@lwn.net,
	Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net-next 0/2] ethtool: add header/data split indication
Date: Thu, 27 Jan 2022 10:42:58 -0800	[thread overview]
Message-ID: <20220127184300.490747-1-kuba@kernel.org> (raw)

TCP ZC Rx requires data to be placed neatly into pages, separate
from the networking headers. This is not supported by most devices
so to make deployment easy this set adds a way for the driver to
report support for this feature thru ethtool.

The larger scope of configuring splitting headers and data, or DMA
scatter seems dauntingly broad, so this set focuses specifically
on the question "is this device usable with TCP ZC Rx?".

The aim is to avoid a litany of conditions on HW platforms, features,
and firmware versions in orchestration systems when the drivers can
easily tell their SG config.

Jakub Kicinski (2):
  ethtool: add header/data split indication
  bnxt: report header-data split state

 Documentation/networking/ethtool-netlink.rst      |  8 ++++++++
 drivers/net/ethernet/broadcom/bnxt/bnxt_ethtool.c |  3 +++
 include/linux/ethtool.h                           |  2 ++
 include/uapi/linux/ethtool_netlink.h              |  7 +++++++
 net/ethtool/rings.c                               | 15 ++++++++++-----
 5 files changed, 30 insertions(+), 5 deletions(-)

-- 
2.34.1


             reply	other threads:[~2022-01-27 18:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27 18:42 Jakub Kicinski [this message]
2022-01-27 18:42 ` [PATCH net-next 1/2] ethtool: add header/data split indication Jakub Kicinski
2022-01-27 18:43 ` [PATCH net-next 2/2] bnxt: report header-data split state Jakub Kicinski
2022-01-28 15:10 ` [PATCH net-next 0/2] ethtool: add header/data split indication 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=20220127184300.490747-1-kuba@kernel.org \
    --to=kuba@kernel.org \
    --cc=chenhao288@hisilicon.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=huangguangbin2@huawei.com \
    --cc=idosch@nvidia.com \
    --cc=linux-doc@vger.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).