From: "Jan Lübbe" <jlu@pengutronix.de>
To: Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>
Cc: netdev <netdev@vger.kernel.org>,
Vivien Didelot <vivien.didelot@savoirfairelinux.com>,
kernel@pengutronix.de, Andrew Lunn <andrew@lunn.ch>
Subject: Re: dsa traffic priorization
Date: Thu, 19 Sep 2019 15:21:50 +0200 [thread overview]
Message-ID: <06d2ca7441c899b4da8475f82dc706351edd0976.camel@pengutronix.de> (raw)
In-Reply-To: <1b80f9ed-7a62-99c4-10bc-bc1887f80867@gmail.com>
Hi,
On Wed, 2019-09-18 at 10:41 -0700, Florian Fainelli wrote:
> > Technically, configuring a match-all rxnfc rule with ethtool would
> > count as 'default priority' - I have proposed that before. Now I'm not
> > entirely sure how intuitive it is, but I'm also interested in being
> > able to configure this.
>
> That does not sound too crazy from my perspective.
Sascha and myself aren't that familiar with that part of ethtool.
You're talking about using ethtool --config-nfc/--config-ntuple on the
(external) sw1p1, sw1p2 ports? Something like this (completely untested
from the manpage):
ethtool --config-nfc sw1p1 flow-type ether queue 2 # high prio queue for ethercat
ethtool --config-nfc sw1p2 flow-type ether queue 1 # normal for rest
Currently, there seems to be no "match-all" option.
Alternatives to "queue X" might be "action" or "context", but I don't
know enough about the details to prefer one above the other.
Regards,
Jan
next prev parent reply other threads:[~2019-09-19 13:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 14:02 dsa traffic priorization Sascha Hauer
2019-09-18 14:36 ` Vladimir Oltean
2019-09-18 15:03 ` Dave Taht
2019-09-18 17:27 ` Florian Fainelli
2019-09-18 17:41 ` Florian Fainelli
2019-09-18 19:39 ` Vladimir Oltean
2019-09-18 22:02 ` Florian Fainelli
2019-09-19 8:44 ` Sascha Hauer
2019-09-19 17:12 ` Florian Fainelli
2019-09-23 12:56 ` Jan Lübbe
2019-09-23 15:32 ` Florian Fainelli
2019-09-19 13:21 ` Jan Lübbe [this message]
2019-09-19 13:33 ` Vladimir Oltean
2019-09-19 13:35 ` Jan Lübbe
2019-09-19 8:00 ` Sascha Hauer
2019-09-19 8:18 ` Vladimir Oltean
2019-09-19 8:41 ` Sascha Hauer
2019-09-19 8:36 ` Uwe Kleine-König
2019-09-19 8:42 ` Vladimir Oltean
2019-09-19 13:34 ` Andrew Lunn
2019-09-19 14:44 ` Jan Lübbe
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=06d2ca7441c899b4da8475f82dc706351edd0976.camel@pengutronix.de \
--to=jlu@pengutronix.de \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=kernel@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=vivien.didelot@savoirfairelinux.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).