From: Petr Machata <petrm@mellanox.com>
To: netdev@vger.kernel.org
Cc: Petr Machata <petrm@mellanox.com>,
Stephen Hemminger <stephen@networkplumber.org>,
David Ahern <dsahern@gmail.com>
Subject: [PATCH iproute2-next v2 0/3] Support pedit of ip6 traffic_class
Date: Sat, 4 Apr 2020 02:05:28 +0300 [thread overview]
Message-ID: <cover.1585954968.git.petrm@mellanox.com> (raw)
The pedit action supports tos (and its synonyms, such as dsfield) for IPv4,
but not the corresponding IPv6 field, traffic_class. Patch #1 of this
series adds this IPv6 support. Patch #2 then adds two related examples to
man page, and patch #3 removes from the man page a claim that the extended
notation is only available for IPv4.
v2:
- Patch #1:
- Only accept 'traffic_class'.
- Move the if-branch that matches it to the end of the list.
- man: Drop the untrue statement that the traffic_class field needs
to be sandwiched between two 4-bit zeroes.
Petr Machata (3):
tc: p_ip6: Support pedit of IPv6 dsfield
man: tc-pedit: Add examples for dsfield and retain
man: tc-pedit: Drop the claim that pedit ex is only for IPv4
man/man8/tc-pedit.8 | 31 +++++++++++++++++++++++++++----
tc/p_ip6.c | 15 +++++++++++++++
2 files changed, 42 insertions(+), 4 deletions(-)
--
2.20.1
next reply other threads:[~2020-04-03 23:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 23:05 Petr Machata [this message]
2020-04-03 23:05 ` [PATCH iproute2-next v2 1/3] tc: p_ip6: Support pedit of IPv6 dsfield Petr Machata
2020-04-03 23:05 ` [PATCH iproute2-next v2 2/3] man: tc-pedit: Add examples for dsfield and retain Petr Machata
2020-04-03 23:05 ` [PATCH iproute2-next v2 3/3] man: tc-pedit: Drop the claim that pedit ex is only for IPv4 Petr Machata
2020-04-09 14:41 ` [PATCH iproute2-next v2 0/3] Support pedit of ip6 traffic_class David Ahern
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=cover.1585954968.git.petrm@mellanox.com \
--to=petrm@mellanox.com \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.