From: "Łukasz Majewski" <lukma@nabladev.com>
To: Frieder Schrempf <frieder.schrempf@kontron.de>
Cc: Woojung.Huh@microchip.com, kuba@kernel.org, andrew@lunn.ch,
netdev@vger.kernel.org, Tristram.Ha@microchip.com
Subject: Re: KSZ9477 HSR Offloading
Date: Wed, 13 Aug 2025 15:54:52 +0200 [thread overview]
Message-ID: <20250813155452.55c4eb81@wsk> (raw)
In-Reply-To: <8e761c31-728c-4ff7-925a-5e16a9ef1310@kontron.de>
Hi Frieder,
> Am 04.02.25 um 15:55 schrieb Woojung.Huh@microchip.com:
> > Hi Jakub,
> >
> >> -----Original Message-----
> >> From: Jakub Kicinski <kuba@kernel.org>
> >> Sent: Monday, February 3, 2025 6:04 PM
> >> To: Woojung Huh - C21699 <Woojung.Huh@microchip.com>
> >> Cc: frieder.schrempf@kontron.de; lukma@denx.de; andrew@lunn.ch;
> >> netdev@vger.kernel.org; Tristram Ha - C24268
> >> <Tristram.Ha@microchip.com> Subject: Re: KSZ9477 HSR Offloading
> >>
> >> EXTERNAL EMAIL: Do not click links or open attachments unless you
> >> know the content is safe
> >>
> >> On Mon, 3 Feb 2025 14:58:12 +0000 Woojung.Huh@microchip.com wrote:
> >>
> >>> Hi Lukasz & Frieder,
> >>>
> >>> Oops! My bad. I confused that Lukasz was filed a case originally.
> >>> Monday
> >> brain-freeze. :(
> >>>
> >>> Yes, it is not a public link and per-user case. So, only Frieder
> >>> can see
> >> it.
> >>> It may be able for you when Frieder adds you as a team. (Not
> >>> tested
> >> personally though)
> >>
> >> Woojung Huh, please make sure the mailing list is informed about
> >> the outcomes. Taking discussion off list to a closed ticketing
> >> system is against community rules. See below, thanks.
> >>
> >> Quoting documentation:
> >>
> >> Open development
> >> ----------------
> >>
> >> Discussions about user reported issues, and development of new
> >> code should be conducted in a manner typical for the larger
> >> subsystem. It is common for development within a single company to
> >> be conducted behind closed doors. However, development and
> >> discussions initiated by community members must not be redirected
> >> from public to closed forums or to private email conversations.
> >> Reasonable exceptions to this guidance include discussions about
> >> security related issues.
> >>
> >> See:
> >> https://www.kernel.org/doc/html/next/maintainer/feature-and-driver-maintainers.html#open-development
> >>
> >
> > Learn new thing today. Didn't know this. Definitely I will share it
> > when this work is done. My intention was for easier work for
> > request than having me as an middleman for the issue.
>
> Here is a follow-up for this thread. I was busy elsewhere, didn't have
> access to the hardware and failed to respond to the comments from
> Microchip support team provided in their internal ticket system.
>
> As a summary, the Microchip support couldn't reproduce my issue on
> their side and asked for further information.
>
> With the hardware now back on my table I was able to do some further
> investigations and found out that this is caused by a misconfiguration
> on my side, that doesn't get handled/prevented by the kernel.
If I remember correctly from the ticket - there was also an issue with
the size of MTU for HSR packets.
Am I correct?
>
> The HW forwarding between HSR ports is configured in
> ksz9477_hsr_join() at the time of creating the HSR interface by
> calling ksz9477_cfg_port_member().
>
> In my case I enabled the ports **after** that which caused the
> forwarding to be disabled again as ksz9477_cfg_port_member() gets
> called with the default configuration.
>
> If I reorder my commands everything seems to work fine even with
> NETIF_F_HW_HSR_FWD enabled.
>
> I wonder if the kernel should handle this case and prevent the
> forwarding configuration to be disabled if HSR is configured? I'll
> have a look if I can come up with a patch for this.
>
Thanks for looking for this issue. I'm looking forward for your
patches.
--
Best regards,
Lukasz Majewski
--
Nabla Software Engineering GmbH
HRB 40522 Augsburg
Phone: +49 821 45592596
E-Mail: office@nabladev.com
Geschftsfhrer : Stefano Babic
next prev parent reply other threads:[~2025-08-13 14:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 16:14 KSZ9477 HSR Offloading Frieder Schrempf
2025-01-28 17:51 ` Andrew Lunn
2025-01-29 7:24 ` Frieder Schrempf
2025-01-29 8:03 ` Frieder Schrempf
2025-01-29 11:17 ` Lukasz Majewski
2025-01-29 11:35 ` Frieder Schrempf
2025-01-29 13:26 ` Andrew Lunn
2025-01-29 13:58 ` Lukasz Majewski
2025-01-29 17:07 ` Frieder Schrempf
2025-01-29 18:57 ` Woojung.Huh
2025-01-30 8:43 ` Frieder Schrempf
2025-01-30 14:17 ` Woojung.Huh
2025-02-03 9:31 ` Lukasz Majewski
2025-02-03 14:43 ` Woojung.Huh
2025-02-03 14:47 ` Frieder Schrempf
2025-02-03 14:58 ` Woojung.Huh
2025-02-03 23:04 ` Jakub Kicinski
2025-02-04 14:55 ` Woojung.Huh
2025-08-13 13:43 ` Frieder Schrempf
2025-08-13 13:54 ` Łukasz Majewski [this message]
2025-08-13 15:42 ` Frieder Schrempf
2025-08-14 22:55 ` Andrew Lunn
2025-01-29 22:52 ` Lukasz Majewski
2025-01-30 10:19 ` Frieder Schrempf
2025-01-30 10:36 ` Frieder Schrempf
2025-01-30 13:39 ` Andrew Lunn
2025-01-29 13:14 ` Andrew Lunn
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=20250813155452.55c4eb81@wsk \
--to=lukma@nabladev.com \
--cc=Tristram.Ha@microchip.com \
--cc=Woojung.Huh@microchip.com \
--cc=andrew@lunn.ch \
--cc=frieder.schrempf@kontron.de \
--cc=kuba@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.