From: Linus Walleij <linus.walleij@linaro.org>
To: Hans Ulli Kroll <ulli.kroll@googlemail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Vladimir Oltean <olteanv@gmail.com>,
Household Cang <canghousehold@aol.com>
Cc: netdev@vger.kernel.org, Linus Walleij <linus.walleij@linaro.org>,
Maxime Chevallier <maxime.chevallier@bootlin.com>
Subject: [PATCH net v4 0/3] Fix a regression in the Gemini ethernet controller.
Date: Fri, 22 Dec 2023 18:36:34 +0100 [thread overview]
Message-ID: <20231222-new-gemini-ethernet-regression-v4-0-a36e71b0f32b@linaro.org> (raw)
These fixes were developed on top of the earlier fixes.
Finding the right solution is hard because the Gemini checksumming
engine is completely undocumented in the datasheets.
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
---
Changes in v4:
- Properly drop all MTU/TSO muckery in the TX function, the
whole approach is bogus.
- Make the raw etherype retrieveal return __be16, it is the
callers job to deal with endianness (as per the pattern
from if_vlan.h)
- Use __vlan_get_protocol() instead of vlan_get_protocol()
- Only actively bypass the TSS if the frame is over a certain
size.
- Drop comment that no longer applies.
- Link to v3: https://lore.kernel.org/r/20231221-new-gemini-ethernet-regression-v3-0-a96b4374bfe8@linaro.org
Changes in v3:
- Fix a whitespace bug in the first patch.
- Add generic accessors to obtain the raw ethertype of an
ethernet frame. VLAN already have the right accessors.
- Link to v2: https://lore.kernel.org/r/20231216-new-gemini-ethernet-regression-v2-0-64c269413dfa@linaro.org
Changes in v2:
- Drop the TSO and length checks altogether, this was never
working properly.
- Plan to make a proper TSO implementation in the next kernel
cycle.
- Link to v1: https://lore.kernel.org/r/20231215-new-gemini-ethernet-regression-v1-0-93033544be23@linaro.org
---
Linus Walleij (3):
net: ethernet: cortina: Drop software checksum and TSO
if_ether: Add an accessor to read the raw ethertype
net: ethernet: cortina: Bypass checksumming engine of alien ethertypes
drivers/net/ethernet/cortina/gemini.c | 62 +++++++++++++++--------------------
include/linux/if_ether.h | 16 +++++++++
2 files changed, 42 insertions(+), 36 deletions(-)
---
base-commit: 33cc938e65a98f1d29d0a18403dbbee050dcad9a
change-id: 20231203-new-gemini-ethernet-regression-3c672de9cfd9
Best regards,
--
Linus Walleij <linus.walleij@linaro.org>
next reply other threads:[~2023-12-22 17:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 17:36 Linus Walleij [this message]
2023-12-22 17:36 ` [PATCH net v4 1/3] net: ethernet: cortina: Drop software checksum and TSO Linus Walleij
2023-12-22 17:36 ` [PATCH net v4 2/3] if_ether: Add an accessor to read the raw ethertype Linus Walleij
2023-12-22 17:36 ` [PATCH net v4 3/3] net: ethernet: cortina: Bypass checksumming engine of alien ethertypes Linus Walleij
2023-12-29 23:17 ` [PATCH net v4 0/3] Fix a regression in the Gemini ethernet controller Linus Walleij
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=20231222-new-gemini-ethernet-regression-v4-0-a36e71b0f32b@linaro.org \
--to=linus.walleij@linaro.org \
--cc=canghousehold@aol.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=ulli.kroll@googlemail.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).