netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Allan W. Nielsen" <Allan.Nielsen@microchip.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Petr Machata <petrm@nvidia.com>, <Daniel.Machon@microchip.com>,
	<netdev@vger.kernel.org>, <vinicius.gomes@intel.com>,
	<vladimir.oltean@nxp.com>, <thomas.petazzoni@bootlin.com>,
	<maxime.chevallier@bootlin.com>, <roopa@nvidia.com>
Subject: Re: Basic PCP/DEI-based queue classification
Date: Mon, 29 Aug 2022 09:53:42 +0200	[thread overview]
Message-ID: <20220829075342.5ztd5hf4sznl7req@lx-anielsen> (raw)
In-Reply-To: <20220824175453.0bc82031@kernel.org>

Hi,

On 24.08.2022 17:54, Jakub Kicinski wrote:
>For an uneducated maintainer like myself, how do embedded people look
>at DCB? Only place I've seen it used is in RDMA clusers. I suggested
>to Vladimir to look at DCBNL for frame preemption because it's the only
>existing API we have that's vaguely relevant to HW/prio control but he
>ended up going with ethtool.
>No preference here, just trying to map it out in my head.

As I work toghether with Daniel, I'm biased. But I work a lot with
embedded devices ;-)

I think this feature belong in DCB simply because DCB already have the
related configurations (like the default prio, priority-flow-control
etc), and it will be more logical for the user to find the PCP mapping
in the same place.

I think that framepreemption should be in ethtool as it is partly
defined in IEEE802.3 (the physical layer) and it is ethernet only
technology.

/Allan

  parent reply	other threads:[~2022-08-29  7:55 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 [this message]
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

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=20220829075342.5ztd5hf4sznl7req@lx-anielsen \
    --to=allan.nielsen@microchip.com \
    --cc=Daniel.Machon@microchip.com \
    --cc=kuba@kernel.org \
    --cc=maxime.chevallier@bootlin.com \
    --cc=netdev@vger.kernel.org \
    --cc=petrm@nvidia.com \
    --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).