From: Amir Vadai <amir@vadai.me>
To: "Rosen, Rami" <rami.rosen@intel.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
"David S. Miller" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Or Gerlitz <ogerlitz@mellanox.com>,
Hadar Har-Zion <hadarh@mellanox.com>,
Roi Dayan <roid@mellanox.com>
Subject: Re: [PATCH iproute2 2/2] tc/act_tunnel: Introduce ip tunnel action
Date: Tue, 22 Nov 2016 09:50:34 +0200 [thread overview]
Message-ID: <20161122075034.GB12067@office.localdomain> (raw)
In-Reply-To: <9B0331B6EBBD0E4684FBFAEDA55776F93D345ED8@HASMSX110.ger.corp.intel.com>
On Mon, Nov 21, 2016 at 11:50:03PM +0000, Rosen, Rami wrote:
> Hi, Amir,
>
> Following are three minor comments:
>
> Seems that TCA_TUNNEL_KEY_PAD used anywhere:
I assume you ment that it is _NOT_ used anywhere:
This attribute type is used in the kernel side only - for padding 64bit
attributes. The userspace enum should match the kernel include/uapi one.
>
> + TCA_TUNNEL_KEY_PAD,
> + __TCA_TUNNEL_KEY_MAX,
> +};
>
>
> Should be "and destination IP 11.11.0.2" instead of "and destination IP 11.11.0.1":
ack
>
> +Tunnel ID (for example VNI in VXLAN tunnel) .TP .B src_ip Outer header
> +source IP address (IPv4 or IPv6) .TP .B dst_ip Outer header destination
> +IP address (IPv4 or IPv6) .RE .SH EXAMPLES The following example
> +encapsulates incoming ICMP packets on eth0 into a vxlan tunnel by
> +setting metadata to VNI 11, source IP 11.11.0.1 and destination IP
> +11.11.0.1 by forwarding the skb with the metadata to device vxlan0,
> +which will prepare the VXLAN headers:
> +
> +.RS
> +.EX
> +#tc qdisc add dev eth0 handle ffff: ingress #tc filter add dev eth0
> +protocol ip parent ffff: \\
> + flower \\
> + ip_proto icmp \\
> + action tunnel_key set \\
> + src_ip 11.11.0.1 \\
> + dst_ip 11.11.0.2 \\
> + id 11 \\
>
>
> Typo: should be "ip tunnel" instead of "ip tunel":
ack
>
> + * m_tunnel_key.c ip tunel manipulation module
> + *
> + * This program is free software; you can redistribute it and/or
>
> Keep on the good work!
Thanks for reviewing,
Amir
>
> Regards,
> Rami Rosen
> Intel Corporation
next prev parent reply other threads:[~2016-11-22 7:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 10:20 [PATCH iproute2 0/2] tc/cls_flower: Support for ip tunnel metadata set/release/classify Amir Vadai
2016-11-21 10:20 ` [PATCH iproute2 1/2] tc/cls_flower: Classify packet in ip tunnels Amir Vadai
2016-11-21 10:20 ` [PATCH iproute2 2/2] tc/act_tunnel: Introduce ip tunnel action Amir Vadai
2016-11-21 23:50 ` Rosen, Rami
2016-11-22 7:50 ` Amir Vadai [this message]
2016-11-24 13:38 ` [PATCH iproute2 0/2] tc/cls_flower: Support for ip tunnel metadata set/release/classify Jiri Benc
2016-11-24 15:06 ` Amir Vadai
2016-11-24 15:33 ` Jiri Benc
2016-11-27 10:35 ` Amir Vadai
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=20161122075034.GB12067@office.localdomain \
--to=amir@vadai.me \
--cc=davem@davemloft.net \
--cc=hadarh@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=rami.rosen@intel.com \
--cc=roid@mellanox.com \
--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 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).