From: Daniel Machon <daniel.machon@microchip.com>
To: <netdev@vger.kernel.org>
Cc: <Allan.Nielsen@microchip.com>, <UNGLinuxDriver@microchip.com>,
<maxime.chevallier@bootlin.com>, <vladimir.oltean@nxp.com>,
<petrm@nvidia.com>, <kuba@kernel.org>, <vinicius.gomes@intel.com>,
<thomas.petazzoni@bootlin.com>,
Daniel Machon <daniel.machon@microchip.com>
Subject: [RFC PATCH iproute2-next 0/2] Add pcp-prio and new APPTRUST subcommand
Date: Fri, 9 Sep 2022 12:36:59 +0200 [thread overview]
Message-ID: <20220909103701.468717-1-daniel.machon@microchip.com> (raw)
This patch series implements the interfaces of the kernel side patch series:
https://lore.kernel.org/netdev/20220908120442.3069771-1-daniel.machon@microchip.com/#t
This is posted RFC as the kernel side is not ready to be merged yet.
- New pcp-prio parameter has been added to existing app subcommand.
- New apptrust subcommand with parameter trust-order has been added.
Patch #1 Introduces a new pcp-prio parameter to the app subcommand. This new
parameter uses the array parameter to map a pcp and dei value to priority.
The key is the PCP and DEI value in numerical and symbolic form, respectively.
Also dcb-app.8 man page has been extended to describe the new parameter.
Example:
Map PCP 1 and DEI 0 to priority 1
$ dcb app add dev eth0 pcp-prio 1:1
Map PCP 1 and DEI 1 to priority 1
$ dcb app add dev eth0 pcp-prio 1de:1
Patch #2 Introduces a new apptrust subcommand. This new subcommand has currently
one parameter: trust-order. It lets you specify a list of trusted selectors, in
order of precendence. Also a new dcb-apptrust.8 man page has been added, to
describe the ned subcommand and its parameter.
Example:
Trust selectors dscp and pcp, in that order:
$ dcb apptrust set dev eth0 dscp pcp
Trust selectors ethertype, stream and pcp, in that order
$ dcb apptrust set dev eth0 eth stream pcp
Show the trust order
$ dcb apptrust show dev eth0
trust-order: eth stream pcp
Both patches makes changes to the uapi dcbnl.h kernel header. Changes to kernel
headers is probably not dealt with this way?
Daniel Machon (2):
dcb: add new pcp-prio parameter to dcb app
dcb: add new subcommand for apptrust object
dcb/Makefile | 3 +-
dcb/dcb.c | 4 +-
dcb/dcb.h | 4 +
dcb/dcb_app.c | 70 ++++++++++++
dcb/dcb_apptrust.c | 216 +++++++++++++++++++++++++++++++++++++
include/uapi/linux/dcbnl.h | 15 +++
man/man8/dcb-app.8 | 25 +++++
man/man8/dcb-apptrust.8 | 122 +++++++++++++++++++++
8 files changed, 457 insertions(+), 2 deletions(-)
create mode 100644 dcb/dcb_apptrust.c
create mode 100644 man/man8/dcb-apptrust.8
--
2.34.1
next reply other threads:[~2022-09-09 10:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 10:36 Daniel Machon [this message]
2022-09-09 10:37 ` [RFC PATCH iproute2-next 1/2] dcb: add new pcp-prio parameter to dcb app Daniel Machon
2022-09-09 10:37 ` [RFC PATCH iproute2-next 2/2] dcb: add new subcommand for apptrust object Daniel Machon
2022-09-09 15:06 ` Stephen Hemminger
2022-09-12 6:09 ` Daniel.Machon
2022-09-12 16:34 ` 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=20220909103701.468717-1-daniel.machon@microchip.com \
--to=daniel.machon@microchip.com \
--cc=Allan.Nielsen@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=kuba@kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=petrm@nvidia.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=vinicius.gomes@intel.com \
--cc=vladimir.oltean@nxp.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;
as well as URLs for NNTP newsgroup(s).