From: Andrew Lunn <andrew@lunn.ch>
To: Murali Karicheri <m-karicheri2@ti.com>
Cc: netdev@vger.kernel.org, "Kwok, WingMan" <w-kwok2@ti.com>,
vivien.didelot@gmail.com, f.fainelli@gmail.com, jiri@resnulli.us,
ivecera@redhat.com
Subject: Re: RSTP with switchdev question
Date: Tue, 17 Dec 2019 12:21:22 +0100 [thread overview]
Message-ID: <20191217112122.GB17965@lunn.ch> (raw)
In-Reply-To: <7ca19413-1ac5-946c-c4d0-3d9d5d88e634@ti.com>
On Mon, Dec 16, 2019 at 11:55:05AM -0500, Murali Karicheri wrote:
> + switchdev/DSA experts
Hi Murali
I did not reply before because this is a pure switchdev issue. DSA
does things differently. The kernel FDB and the switches FDB are not
kept in sync. With DSA, when a port changes state, we flush the switch
FDB. For STP, that seems to be sufficient. There have been reports for
RSTP this might not be enough, but that conversation did not go very
far.
I've no idea how this is supposed to work with a pure switchdev
driver. Often, to answer a question like this, you need to take a step
backwards. How is this supposed to work for a machine with two e1000e
cards and a plain software bridge? What ever APIs user space RSTP is
using in a pure software case should be used in a switchdev setup as
well, but extra plumbing in the kernel might be required, and it
sounds like it may be missing...
Andrew
next prev parent reply other threads:[~2019-12-17 11:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 21:18 RSTP with switchdev question Murali Karicheri
2019-12-16 16:55 ` Murali Karicheri
2019-12-17 11:21 ` Andrew Lunn [this message]
2019-12-19 17:30 ` Murali Karicheri
2019-12-19 18:06 ` 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=20191217112122.GB17965@lunn.ch \
--to=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=m-karicheri2@ti.com \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.com \
--cc=w-kwok2@ti.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).