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
Subject: Re: [PATCH net-next v1 2/2] net: dsa: microchip: Add partial ACL support for ksz9477 switches
Date: Mon, 17 Apr 2023 15:05:54 +0300 [thread overview]
Message-ID: <20230417120554.gyrintyd2urredak@skbuf> (raw)
In-Reply-To: <20230417114130.GB11474@pengutronix.de>
On Mon, Apr 17, 2023 at 01:41:30PM +0200, Oleksij Rempel wrote:
> According to my tests, ACL has higher priority compared to 802.1p module.
>
> dcbnl is a new word for me, will need to understand if first :)
> What is the best example to use it with DSCP?
https://github.com/Mellanox/mlxsw/wiki/Quality-of-Service
tools/testing/selftests/drivers/net/ocelot/basic_qos.sh
next prev parent reply other threads:[~2023-04-17 12:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 17:24 [PATCH net-next v1 0/2] net: dsa: microchip: Rework ksz_prmw8 and add partial ACL support Oleksij Rempel
2023-04-11 17:24 ` [PATCH net-next v1 1/2] net: dsa: microchip: rework ksz_prmw8 Oleksij Rempel
2023-04-11 17:24 ` [PATCH net-next v1 2/2] net: dsa: microchip: Add partial ACL support for ksz9477 switches Oleksij Rempel
2023-04-12 5:36 ` kernel test robot
2023-04-13 4:29 ` Oleksij Rempel
2023-04-16 16:59 ` Vladimir Oltean
2023-04-17 11:41 ` Oleksij Rempel
2023-04-17 12:05 ` Vladimir Oltean [this message]
2023-04-18 7:24 ` Oleksij Rempel
2023-04-18 12:08 ` Vladimir Oltean
2023-04-16 16:56 ` Vladimir Oltean
2023-04-17 4:57 ` Oleksij Rempel
2023-04-17 10:12 ` Vladimir Oltean
2023-04-17 11:03 ` Oleksij Rempel
2023-04-17 12:19 ` Vladimir Oltean
2023-04-18 4:55 ` Oleksij Rempel
2023-04-17 14:16 ` kernel test robot
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=20230417120554.gyrintyd2urredak@skbuf \
--to=olteanv@gmail.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=arun.ramadoss@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--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=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