From: Sean Anderson <sean.anderson@linux.dev>
To: Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Michal Simek <michal.simek@amd.com>,
Sean Anderson <sean.anderson@linux.dev>
Subject: [PATCH net-next v2 0/4] net: xilinx: axienet: Partial checksum offload improvements
Date: Mon, 9 Sep 2024 12:10:12 -0400 [thread overview]
Message-ID: <20240909161016.1149119-1-sean.anderson@linux.dev> (raw)
Partial checksum offload is not always used when it could be. Enable it
in more cases.
Changes in v2:
- Set RXCSUM in features
- Expand commit message with testing methodology
Sean Anderson (4):
net: xilinx: axienet: Remove unused checksum variables
net: xilinx: axienet: Enable NETIF_F_HW_CSUM for partial tx
checksumming
net: xilinx: axienet: Set RXCSUM in features
net: xilinx: axienet: Relax partial rx checksum checks
drivers/net/ethernet/xilinx/xilinx_axienet.h | 5 -----
.../net/ethernet/xilinx/xilinx_axienet_main.c | 22 +++++--------------
2 files changed, 5 insertions(+), 22 deletions(-)
--
2.35.1.1320.gc452695387.dirty
next reply other threads:[~2024-09-09 16:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 16:10 Sean Anderson [this message]
2024-09-09 16:10 ` [PATCH net-next v2 1/4] net: xilinx: axienet: Remove unused checksum variables Sean Anderson
2024-09-09 16:10 ` [PATCH net-next v2 2/4] net: xilinx: axienet: Enable NETIF_F_HW_CSUM for partial tx checksumming Sean Anderson
2024-09-09 16:10 ` [PATCH net-next v2 3/4] net: xilinx: axienet: Set RXCSUM in features Sean Anderson
2024-09-09 16:10 ` [PATCH net-next v2 4/4] net: xilinx: axienet: Relax partial rx checksum checks Sean Anderson
2024-09-11 2:10 ` [PATCH net-next v2 0/4] net: xilinx: axienet: Partial checksum offload improvements 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=20240909161016.1149119-1-sean.anderson@linux.dev \
--to=sean.anderson@linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=radhey.shyam.pandey@amd.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;
as well as URLs for NNTP newsgroup(s).