From: Andrew Lunn <andrew@lunn.ch>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: Luiz Angelo Daros de Luca <luizluca@gmail.com>,
Kurt Kanzenbach <kurt@linutronix.de>,
George McCollister <george.mccollister@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH net-next v2] docs: net: dsa: describe issues with checksum offload
Date: Wed, 13 Apr 2022 22:56:12 +0200 [thread overview]
Message-ID: <Ylc47F5w/rgzGx1x@lunn.ch> (raw)
In-Reply-To: <20220413200841.4nmnv2qgapqhfnx3@skbuf>
On Wed, Apr 13, 2022 at 08:08:41PM +0000, Vladimir Oltean wrote:
> I've copied a bunch of new people to this email.
>
> TL;DR: Kurt/George/Andrew, on your systems with hellcreek/xrs700x/mv88e6060,
> does the DSA master declare any of the following features as "on"?
>
> ethtool -k eth0 | grep tx-checksum-ip
>
> I would expect not. Otherwise, we've either found a bug, or discovered the Sasquatch.
Easier than i was expecting. As i said, Marvell Kirkwood with a
mv643xx as master:
root@dir665:~# ethtool -k eth0 | grep tx-checksum-ip
tx-checksum-ipv4: on
tx-checksum-ip-generic: off [fixed]
tx-checksum-ipv6: off [fixed]
Andrew
next prev parent reply other threads:[~2022-04-13 20:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 23:03 [PATCH net-next v2] docs: net: dsa: describe issues with checksum offload Luiz Angelo Daros de Luca
2022-04-13 20:08 ` Vladimir Oltean
2022-04-13 20:49 ` Andrew Lunn
2022-04-13 20:53 ` Vladimir Oltean
2022-04-13 20:57 ` Andrew Lunn
2022-04-13 21:00 ` Vladimir Oltean
2022-04-14 2:48 ` Luiz Angelo Daros de Luca
2022-04-14 12:58 ` Vladimir Oltean
2022-04-15 8:01 ` Luiz Angelo Daros de Luca
2022-04-15 10:22 ` Vladimir Oltean
2022-04-16 5:30 ` Luiz Angelo Daros de Luca
2022-04-13 20:56 ` Andrew Lunn [this message]
2022-04-14 6:29 ` Kurt Kanzenbach
2022-04-14 15:22 ` Vladimir Oltean
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=Ylc47F5w/rgzGx1x@lunn.ch \
--to=andrew@lunn.ch \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=george.mccollister@gmail.com \
--cc=kuba@kernel.org \
--cc=kurt@linutronix.de \
--cc=linux-doc@vger.kernel.org \
--cc=luizluca@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vladimir.oltean@nxp.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).