From: Petr Machata <petrm@nvidia.com>
To: <Daniel.Machon@microchip.com>
Cc: <petrm@nvidia.com>, <netdev@vger.kernel.org>, <kuba@kernel.org>,
<vinicius.gomes@intel.com>, <vladimir.oltean@nxp.com>,
<thomas.petazzoni@bootlin.com>, <Allan.Nielsen@microchip.com>,
<maxime.chevallier@bootlin.com>, <roopa@nvidia.com>
Subject: Re: Basic PCP/DEI-based queue classification
Date: Thu, 25 Aug 2022 15:30:58 +0200 [thread overview]
Message-ID: <87fshkjv9l.fsf@nvidia.com> (raw)
In-Reply-To: <Ywdff/6c3nRMRHDb@DEN-LT-70577>
<Daniel.Machon@microchip.com> writes:
> I will prepare some patches for this soon and make sure to cc you.
> Initially I would like to add support for:
>
> - pcp/dei-prio mapping for ingress only. If things look good, we
> can add support for rewrite later. Any objections to this?
Rewrite is closely related, but we don't have tools to configure it
anyway, and I don't see how adding a PCP prioritization first makes it
more difficult to add these later.
> - Support for trust ordering as a new dedicated object.
Sounds good.
But note that I'm not a gatekeeper, I just happened on some opinions :)
prev parent reply other threads:[~2022-08-25 13:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 9:09 Basic PCP/DEI-based queue classification Daniel.Machon
2022-08-19 10:50 ` Petr Machata
2022-08-21 20:58 ` Daniel.Machon
2022-08-22 10:34 ` Petr Machata
2022-08-24 7:39 ` Daniel.Machon
2022-08-24 9:45 ` Petr Machata
2022-08-24 17:55 ` Daniel.Machon
2022-08-24 19:36 ` Petr Machata
2022-08-25 0:54 ` Jakub Kicinski
2022-08-26 18:11 ` Petr Machata
2022-08-29 7:53 ` Allan W. Nielsen
2022-09-02 13:32 ` Vladimir Oltean
2022-09-07 10:41 ` Daniel.Machon
2022-09-07 17:26 ` Vladimir Oltean
2022-09-07 19:57 ` Daniel.Machon
2022-09-08 8:03 ` Allan Nielsen - M31684
2022-09-08 11:18 ` Petr Machata
2022-09-08 12:01 ` Daniel.Machon
2022-09-09 12:11 ` Vladimir Oltean
2022-09-08 8:27 ` Petr Machata
2022-08-25 11:31 ` Daniel.Machon
2022-08-25 13:30 ` Petr Machata [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=87fshkjv9l.fsf@nvidia.com \
--to=petrm@nvidia.com \
--cc=Allan.Nielsen@microchip.com \
--cc=Daniel.Machon@microchip.com \
--cc=kuba@kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@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).