From: Petr Machata <petrm@nvidia•com>
To: Daniel Machon <daniel.machon@microchip•com>
Cc: <netdev@vger•kernel.org>, <dsahern@kernel•org>,
<stephen@networkplumber•org>, <petrm@nvidia•com>,
<maxime.chevallier@bootlin•com>, <vladimir.oltean@nxp•com>,
<UNGLinuxDriver@microchip•com>
Subject: Re: [PATCH iproute2-next v2 1/2] dcb: add new pcp-prio parameter to dcb app
Date: Tue, 29 Nov 2022 10:35:08 +0100 [thread overview]
Message-ID: <87wn7ef6ai.fsf@nvidia.com> (raw)
In-Reply-To: <20221128123817.2031745-2-daniel.machon@microchip.com>
Daniel Machon <daniel.machon@microchip•com> writes:
> Add new pcp-prio parameter to the app subcommand, which can be used to
> classify traffic based on PCP and DEI from the VLAN header. PCP and DEI
> is specified in a combination of numerical and symbolic form, where 'de'
> (drop-eligible) means DEI=1 and 'nd' (not-drop-eligible) means DEI=0.
>
> Map PCP 1 and DEI 0 to priority 1
> $ dcb app add dev eth0 pcp-prio 1nd:1
>
> Map PCP 1 and DEI 1 to priority 1
> $ dcb app add dev eth0 pcp-prio 1de:1
>
> Internally, PCP and DEI is encoded in the protocol field of the dcb_app
> struct. Each combination of PCP and DEI maps to a priority, thus needing
> a range of 0-15. A well formed dcb_app entry for PCP/DEI
> prioritization, could look like:
>
> struct dcb_app pcp = {
> .selector = DCB_APP_SEL_PCP,
> .priority = 7,
> .protocol = 15
> }
>
> For mapping PCP=7 and DEI=1 to Prio=7.
>
> Also, three helper functions for translating between std and non-std APP
> selectors, have been added to dcb_app.c and exposed through dcb.h.
>
> Signed-off-by: Daniel Machon <daniel.machon@microchip•com>
Reviewed-by: Petr Machata <petrm@nvidia•com>
next prev parent reply other threads:[~2022-11-29 9:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 12:38 [PATCH iproute2-next v2 0/2] Add pcp-prio and new apptrust subcommand Daniel Machon
2022-11-28 12:38 ` [PATCH iproute2-next v2 1/2] dcb: add new pcp-prio parameter to dcb app Daniel Machon
2022-11-29 9:35 ` Petr Machata [this message]
2022-12-01 6:43 ` David Ahern
2022-12-01 10:57 ` Petr Machata
2022-12-01 14:10 ` Petr Machata
2022-12-02 8:45 ` Daniel.Machon
2022-11-28 12:38 ` [PATCH iproute2-next v2 2/2] dcb: add new subcommand for apptrust Daniel Machon
2022-11-29 9:24 ` Petr Machata
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=87wn7ef6ai.fsf@nvidia.com \
--to=petrm@nvidia$(echo .)com \
--cc=UNGLinuxDriver@microchip$(echo .)com \
--cc=daniel.machon@microchip$(echo .)com \
--cc=dsahern@kernel$(echo .)org \
--cc=maxime.chevallier@bootlin$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=stephen@networkplumber$(echo .)org \
--cc=vladimir.oltean@nxp$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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