From: Ziwei Xiao <ziweixiao@google.com>
To: netdev@vger.kernel.org
Cc: jeroendb@google.com, pkaligineedi@google.com,
shailend@google.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, willemb@google.com,
rushilg@google.com, jfraker@google.com, jrkim@google.com,
hramamurthy@google.com, ziweixiao@google.com, horms@kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH net-next 0/3] gve: Add header split support
Date: Thu, 29 Feb 2024 13:22:33 -0800 [thread overview]
Message-ID: <20240229212236.3152897-1-ziweixiao@google.com> (raw)
Currently, the ethtool's ringparam has added a new field tcp-data-split
for enabling and disabling header split. These three patches will
utilize that ethtool flag to support header split in GVE driver.
Jeroen de Borst (3):
gve: Add header split device option
gve: Add header split data path
gve: Add header split ethtool stats
drivers/net/ethernet/google/gve/gve.h | 27 +++++++-
drivers/net/ethernet/google/gve/gve_adminq.c | 50 ++++++++++++--
drivers/net/ethernet/google/gve/gve_adminq.h | 20 +++++-
drivers/net/ethernet/google/gve/gve_ethtool.c | 62 +++++++++++++----
drivers/net/ethernet/google/gve/gve_main.c | 65 ++++++++++++++++--
drivers/net/ethernet/google/gve/gve_rx_dqo.c | 68 ++++++++++++++++++-
drivers/net/ethernet/google/gve/gve_utils.c | 17 +++--
drivers/net/ethernet/google/gve/gve_utils.h | 3 +
8 files changed, 277 insertions(+), 35 deletions(-)
--
2.44.0.rc1.240.g4c46232300-goog
next reply other threads:[~2024-02-29 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 21:22 Ziwei Xiao [this message]
2024-02-29 21:22 ` [PATCH net-next 1/3] gve: Add header split device option Ziwei Xiao
2024-02-29 21:22 ` [PATCH net-next 2/3] gve: Add header split data path Ziwei Xiao
2024-02-29 21:22 ` [PATCH net-next 3/3] gve: Add header split ethtool stats Ziwei Xiao
2024-03-04 10:10 ` [PATCH net-next 0/3] gve: Add header split support patchwork-bot+netdevbpf
2024-03-05 2:13 ` Mina Almasry
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=20240229212236.3152897-1-ziweixiao@google.com \
--to=ziweixiao@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=hramamurthy@google.com \
--cc=jeroendb@google.com \
--cc=jfraker@google.com \
--cc=jrkim@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pkaligineedi@google.com \
--cc=rushilg@google.com \
--cc=shailend@google.com \
--cc=willemb@google.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
all inboxes | Powered by JetHome®