public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Petr Machata <petrm@nvidia•com>
To: Daniel Machon <daniel.machon@microchip•com>
Cc: <netdev@vger•kernel.org>, <davem@davemloft•net>,
	<petrm@nvidia•com>, <maxime.chevallier@bootlin•com>,
	<thomas.petazzoni@bootlin•com>, <edumazet@google•com>,
	<kuba@kernel•org>, <pabeni@redhat•com>,
	<lars.povlsen@microchip•com>, <Steen.Hegelund@microchip•com>,
	<UNGLinuxDriver@microchip•com>, <joe@perches•com>,
	<linux@armlinux•org.uk>, <horatiu.vultur@microchip•com>,
	<Julia.Lawall@inria•fr>, <vladimir.oltean@nxp•com>,
	<linux-kernel@vger•kernel.org>,
	<linux-arm-kernel@lists•infradead.org>
Subject: Re: [PATCH net-next v6 1/6] net: dcb: add new pcp selector to app object
Date: Tue, 1 Nov 2022 15:02:39 +0100	[thread overview]
Message-ID: <87edumvkkx.fsf@nvidia.com> (raw)
In-Reply-To: <20221101094834.2726202-2-daniel.machon@microchip.com>


Daniel Machon <daniel.machon@microchip•com> writes:

> Add new PCP selector for the 8021Qaz APP managed object.
>
> As the PCP selector is not part of the 8021Qaz standard, a new non-std
> extension attribute DCB_ATTR_DCB_APP has been introduced. Also two
> helper functions to translate between selector and app attribute type
> has been added. The new selector has been given a value of 255, to
> minimize the risk of future overlap of std- and non-std attributes.
>
> The new DCB_ATTR_DCB_APP is sent alongside the ieee std attribute in the
> app table. This means that the dcb_app struct can now both contain std-
> and non-std app attributes. Currently there is no overlap between the
> selector values of the two attributes.
>
> The purpose of adding the PCP selector, is to be able to offload
> PCP-based queue classification to the 8021Q Priority Code Point table,
> see 6.9.3 of IEEE Std 802.1Q-2018.
>
> PCP and DEI is encoded in the protocol field as 8*dei+pcp, so that a
> mapping of PCP 2 and DEI 1 to priority 3 is encoded as {255, 10, 3}.
>
> Signed-off-by: Daniel Machon <daniel.machon@microchip•com>

Reviewed-by: Petr Machata <petrm@nvidia•com>

  reply	other threads:[~2022-11-01 14:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01  9:48 [PATCH net-next v6 0/6] Add new PCP and APPTRUST attributes to dcbnl Daniel Machon
2022-11-01  9:48 ` [PATCH net-next v6 1/6] net: dcb: add new pcp selector to app object Daniel Machon
2022-11-01 14:02   ` Petr Machata [this message]
2022-11-01  9:48 ` [PATCH net-next v6 2/6] net: dcb: add new apptrust attribute Daniel Machon
2022-11-01 14:04   ` Petr Machata
2022-11-01  9:48 ` [PATCH net-next v6 3/6] net: microchip: sparx5: add support for offloading pcp table Daniel Machon
2022-11-01  9:48 ` [PATCH net-next v6 4/6] net: microchip: sparx5: add support for apptrust Daniel Machon
2022-11-01  9:48 ` [PATCH net-next v6 5/6] net: microchip: sparx5: add support for offloading dscp table Daniel Machon
2022-11-01  9:48 ` [PATCH net-next v6 6/6] net: microchip: sparx5: add support for offloading default prio Daniel Machon
2022-11-03 14:50 ` [PATCH net-next v6 0/6] Add new PCP and APPTRUST attributes to dcbnl patchwork-bot+netdevbpf

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=87edumvkkx.fsf@nvidia.com \
    --to=petrm@nvidia$(echo .)com \
    --cc=Julia.Lawall@inria$(echo .)fr \
    --cc=Steen.Hegelund@microchip$(echo .)com \
    --cc=UNGLinuxDriver@microchip$(echo .)com \
    --cc=daniel.machon@microchip$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=horatiu.vultur@microchip$(echo .)com \
    --cc=joe@perches$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=lars.povlsen@microchip$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux@armlinux$(echo .)org.uk \
    --cc=maxime.chevallier@bootlin$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=thomas.petazzoni@bootlin$(echo .)com \
    --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