Netdev List
 help / color / mirror / Atom feed
From: Or Gerlitz <ogerlitz@mellanox.com>
To: David Ahern <dsahern@gmail.com>
Cc: netdev@vger.kernel.org, Or Gerlitz <ogerlitz@mellanox.com>
Subject: [PATCH iproute2/next 0/2] set/match the tos/ttl fields of TC based IP tunnels
Date: Thu, 19 Jul 2018 14:02:13 +0300	[thread overview]
Message-ID: <1531998135-13395-1-git-send-email-ogerlitz@mellanox.com> (raw)

Hi Dave,

This series comes to address the case to set (encap) and match (decap)
also the tos and ttl fields of TC based IP tunnels.

Example command lines in the change log of each patch.

The kernel bits are under review [1], sending this out in parallel.

Or.

[1] https://patchwork.ozlabs.org/cover/945216/

Or Gerlitz (2):
  tc/act_tunnel_key: Enable setup of tos and ttl
  tc/flower: Add match on encapsulating tos/ttl

 include/uapi/linux/pkt_cls.h              |    5 +++
 include/uapi/linux/tc_act/tc_tunnel_key.h |    2 +
 man/man8/tc-flower.8                      |   14 +++++++-
 man/man8/tc-tunnel_key.8                  |    8 ++++
 tc/f_flower.c                             |   27 +++++++++++++++
 tc/m_tunnel_key.c                         |   53 +++++++++++++++++++++++++++++
 6 files changed, 108 insertions(+), 1 deletions(-)

             reply	other threads:[~2018-07-19 11:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-19 11:02 Or Gerlitz [this message]
2018-07-19 11:02 ` [PATCH iproute2/next 1/2] tc/act_tunnel_key: Enable setup of tos and ttl Or Gerlitz
2018-07-19 11:48   ` Roman Mashak
2018-07-19 17:14     ` Or Gerlitz
2018-07-19 11:02 ` [PATCH iproute2/next2/next 2/2] tc/flower: Add match on encapsulating tos/ttl Or Gerlitz
2018-07-20 16:01 ` [PATCH iproute2/next 0/2] set/match the tos/ttl fields of TC based IP tunnels 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=1531998135-13395-1-git-send-email-ogerlitz@mellanox.com \
    --to=ogerlitz@mellanox.com \
    --cc=dsahern@gmail.com \
    --cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox