From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Ferenc Fejes <fejes@inf.elte.hu>
Cc: "Péter Antal" <peti.antal99@gmail.com>,
netdev@vger.kernel.org,
"John Fastabend" <john.fastabend@gmail.com>,
"Stephen Hemminger" <stephen@networkplumber.org>,
"Vinicius Costa Gomes" <vinicius.gomes@intel.com>,
"Péter Antal" <antal.peti99@gmail.com>
Subject: Re: [PATCH iproute2] man: tc-mqprio: extend prio-tc-queue mapping with examples
Date: Mon, 20 Feb 2023 17:33:24 +0200 [thread overview]
Message-ID: <20230220153324.h7drlvwtemymqr43@skbuf> (raw)
In-Reply-To: <3e18a65c57ea935ba1ae09fc821197f25a269398.camel@inf.elte.hu>
On Mon, Feb 20, 2023 at 04:15:43PM +0100, Ferenc Fejes wrote:
> Hi!
>
> On Mon, 2023-02-20 at 16:05 +0100, Péter Antal wrote:
> > The current mqprio manual is not detailed about queue mapping
> > and priorities, this patch adds some examples to it.
>
> Thank you Péter for doing this! The same principles however applies to
> tc-taprio as well so it would be nice to see a v2 with those included
> too.
I think that the well-established phrase "See mqprio(8) for more details."
will do just fine.
next prev parent reply other threads:[~2023-02-20 15:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 15:05 [PATCH iproute2] man: tc-mqprio: extend prio-tc-queue mapping with examples Péter Antal
2023-02-20 15:15 ` Ferenc Fejes
2023-02-20 15:33 ` Vladimir Oltean [this message]
2023-02-20 15:29 ` Vladimir Oltean
2023-02-20 16:01 ` Péter Antal
2023-02-20 16:14 ` Ferenc Fejes
2023-02-20 16:18 ` Vladimir Oltean
2023-02-20 16:28 ` Ferenc Fejes
2023-02-20 16:34 ` Péter Antal
2023-03-04 2:20 ` 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=20230220153324.h7drlvwtemymqr43@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=antal.peti99@gmail.com \
--cc=fejes@inf.elte.hu \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=peti.antal99@gmail.com \
--cc=stephen@networkplumber.org \
--cc=vinicius.gomes@intel.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