From: Luke Howard <lukeh@padl.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Vladimir Oltean <olteanv@gmail.com>,
netdev@vger.kernel.org, Kieran Tyrrell <kieran@sienda.com>,
Max Hunter <max@huntershome.org>
Subject: Re: net: dsa: mv88e6xxx architecture
Date: Sun, 22 Dec 2024 09:15:20 +1100 [thread overview]
Message-ID: <C52AE934-0FE9-48C0-A258-F6357E6BBCC2@padl.com> (raw)
In-Reply-To: <5bdb17e0-cd7a-44e3-bdd4-d0686ea61b14@lunn.ch>
> Doesn't FDB/MDB imply you have a bridge? What about an isolated port
> which is not a member of a bridge, there is only local traffic?
I don’t believe local traffic is an issue (if it were, I imagine one could use cgroups to control which processes could send frames of a particular priority). (Kieran, feel free to correct me.)
What I’ve done in the current patch (behind a Kconfig option) is to assume that static FDB/MDB entries on MQPRIO ports are for AVB alone. But this may be incompatible with IGMP snooping, if that also results in the creation of static MDB entires.
Adding MQPRIO/CBS support without this admission control is definitely an option and perhaps a good first step, the proviso being that when bridging, SRP would not provide a guaranteed bandwidth reservation.
next prev parent reply other threads:[~2024-12-21 22:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 21:02 net: dsa: mv88e6xxx architecture Luke Howard
2024-12-20 12:10 ` Vladimir Oltean
2024-12-20 21:46 ` Luke Howard
[not found] ` <7E1DC313-33DE-4AA8-AD52-56316C07ABC4@padl.com>
2024-12-20 22:33 ` Andrew Lunn
2024-12-20 22:56 ` Luke Howard
[not found] ` <F8AE422A-2A10-4C39-A431-DA6E668797D3@padl.com>
2024-12-21 21:36 ` Andrew Lunn
2024-12-21 22:15 ` Luke Howard [this message]
2024-12-20 22:54 ` Vladimir Oltean
2024-12-20 22:59 ` Luke Howard
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=C52AE934-0FE9-48C0-A258-F6357E6BBCC2@padl.com \
--to=lukeh@padl.com \
--cc=andrew@lunn.ch \
--cc=kieran@sienda.com \
--cc=max@huntershome.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.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