From: Vladimir Oltean <olteanv@gmail.com>
To: Luke Howard Bentata <lukeh@padl.com>
Cc: netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Kieran Tyrrell <kieran@sienda.com>,
Max Hunter <max@huntershome.org>
Subject: Re: net: dsa: mv88e6xxx architecture
Date: Sat, 21 Dec 2024 00:54:32 +0200 [thread overview]
Message-ID: <20241220225432.jsgw35gq3ejp57va@skbuf> (raw)
In-Reply-To: <7E1DC313-33DE-4AA8-AD52-56316C07ABC4@padl.com>
On Sat, Dec 21, 2024 at 08:43:50AM +1100, Luke Howard Bentata wrote:
> Hi Vladimir,
>
> > I think we need an AVB primer. What identifies an AVB stream? Should the
> > kernel have a database of them? What actions need to be taken for AVB
> > streams different than for best effort traffic? Is it about scheduling
> > priority, or about resource reservations, or? Does the custom behavior
> > pertain only to AVB streams or is it a more widely useful mechanism?
>
> The catch is what to do with frames that share a priority with an AVB
> class but are not negotiated by SRP. These frames could crowd out
> frames from AVB streams. Marvell’s solution is a flag in the ATU which
> indicates that the DA was added by SRP.
Can you please state in a vendor-agnostic way what does the switch do
with that information, how does it treat those streams specially?
next prev parent reply other threads:[~2024-12-20 22:54 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
2024-12-20 22:54 ` Vladimir Oltean [this message]
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=20241220225432.jsgw35gq3ejp57va@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=kieran@sienda.com \
--cc=lukeh@padl.com \
--cc=max@huntershome.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox