public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Oltean <olteanv@gmail.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: "David S. Miller" <davem@davemloft.net>,
	"Andrew Lunn" <andrew@lunn.ch>,
	"Eric Dumazet" <edumazet@google.com>,
	"Florian Fainelli" <f.fainelli@gmail.com>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Woojung Huh" <woojung.huh@microchip.com>,
	"Arun Ramadoss" <arun.ramadoss@microchip.com>,
	kernel@pengutronix.de, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, UNGLinuxDriver@microchip.com,
	"David Ahern" <dsahern@kernel.org>,
	"Simon Horman" <horms@kernel.org>,
	"Willem de Bruijn" <willemb@google.com>,
	"Søren Andersen" <san@skov.dk>
Subject: Re: [PATCH net-next v6 0/9] Enhanced DCB and DSCP Support for KSZ Switches
Date: Thu, 11 Apr 2024 02:18:49 +0300	[thread overview]
Message-ID: <20240410231849.dmmlhaictptcof2r@skbuf> (raw)
In-Reply-To: <20240410080556.1241048-1-o.rempel@pengutronix.de>

On Wed, Apr 10, 2024 at 10:05:47AM +0200, Oleksij Rempel wrote:
> This patch series is aimed at improving support for DCB (Data Center
> Bridging) and DSCP (Differentiated Services Code Point) on KSZ switches.
> 
> The main goal is to introduce global DSCP and PCP (Priority Code Point)
> mapping support, addressing the limitation of KSZ switches not having
> per-port DSCP priority mapping. This involves extending the DSA
> framework with new callbacks for managing trust settings for global DSCP
> and PCP maps. Additionally, we introduce IEEE 802.1q helpers for default
> configurations, benefiting other drivers too.
> 
> Change logs are in separate patches.

In whichever way this goes, could we also see a selftest in future patch
revisions (similar to tools/testing/selftests/drivers/net/ocelot/basic_qos.sh),
which (beyond the basic task of proving that it works) sets straight the
basic user expectations of _what_ works and can be done in terms of QoS
classification on these switches?

      parent reply	other threads:[~2024-04-10 23:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10  8:05 [PATCH net-next v6 0/9] Enhanced DCB and DSCP Support for KSZ Switches Oleksij Rempel
2024-04-10  8:05 ` [PATCH net-next v6 1/9] net: dsa: add support for DCB get/set apptrust configuration Oleksij Rempel
2024-04-10  8:05 ` [PATCH net-next v6 2/9] net: dsa: microchip: add IPV information support Oleksij Rempel
2024-04-10  8:05 ` [PATCH net-next v6 3/9] net: add IEEE 802.1q specific helpers Oleksij Rempel
2024-04-11 11:46   ` Simon Horman
2024-04-11 11:51   ` Vladimir Oltean
2024-04-10  8:05 ` [PATCH net-next v6 4/9] net: dsa: microchip: add multi queue support for KSZ88X3 variants Oleksij Rempel
2024-04-10  8:05 ` [PATCH net-next v6 5/9] net: dsa: microchip: add support for different DCB app configurations Oleksij Rempel
2024-04-10 15:32   ` Vladimir Oltean
2024-04-10 16:11     ` Oleksij Rempel
2024-04-10 23:12   ` Vladimir Oltean
2024-04-11  6:48     ` Oleksij Rempel
2024-04-11 11:39       ` Vladimir Oltean
2024-04-10  8:05 ` [PATCH net-next v6 6/9] net: dsa: microchip: dcb: add special handling for KSZ88X3 family Oleksij Rempel
2024-04-10  8:05 ` [PATCH net-next v6 7/9] net: dsa: microchip: enable ETS support for KSZ989X variants Oleksij Rempel
2024-04-10  8:05 ` [PATCH net-next v6 8/9] net: dsa: microchip: init predictable IPV to queue mapping for all non KSZ8xxx variants Oleksij Rempel
2024-04-10  8:05 ` [PATCH net-next v6 9/9] net: dsa: microchip: let DCB code do PCP and DSCP policy configuration Oleksij Rempel
2024-04-10 23:18 ` Vladimir Oltean [this message]

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=20240410231849.dmmlhaictptcof2r@skbuf \
    --to=olteanv@gmail.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=arun.ramadoss@microchip.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=horms@kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=pabeni@redhat.com \
    --cc=san@skov.dk \
    --cc=willemb@google.com \
    --cc=woojung.huh@microchip.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