From: David Ahern <dsahern@gmail.com>
To: William Tu <u9012063@gmail.com>, netdev@vger.kernel.org
Subject: Re: [PATCH v4 iproute2 net-next] erspan: add erspan version II support
Date: Mon, 25 Dec 2017 16:44:18 -0600 [thread overview]
Message-ID: <1ac019fb-1a91-3664-affe-43a0d4a3502a@gmail.com> (raw)
In-Reply-To: <1513735266-116453-1-git-send-email-u9012063@gmail.com>
On 12/19/17 8:01 PM, William Tu wrote:
> The patch adds support for configuring the erspan v2, for both
> ipv4 and ipv6 erspan implementation. Three additional fields
> are added: 'erspan_ver' for distinguishing v1 or v2, 'erspan_dir'
> for specifying direction of the mirrored traffic, and 'erspan_hwid'
> for users to set ERSPAN engine ID within a system.
>
> As for manpage, the ERSPAN descriptions used to be under GRE, IPIP,
> SIT Type paragraph. Since IP6GRE/IP6GRETAP also supports ERSPAN,
> the patch removes the old one, creates a separate ERSPAN paragrah,
> and adds an example.
>
> Signed-off-by: William Tu <u9012063@gmail.com>
> ---
> change in v4:
> - use matches instead of strcmp on ingress/egress
> change in v3:
> - change erspan_dir 0/1 to "in[gress]/e[gress]"
> - update manpage
> change in v2:
> - fix typo ETH_P_ERSPAN2
> - fix space and indent
> ---
> include/uapi/linux/if_ether.h | 1 +
> include/uapi/linux/if_tunnel.h | 3 ++
> ip/link_gre.c | 66 ++++++++++++++++++++++++++++--
> ip/link_gre6.c | 67 ++++++++++++++++++++++++++++--
> man/man8/ip-link.8.in | 92 ++++++++++++++++++++++++++++++++++++------
> 5 files changed, 210 insertions(+), 19 deletions(-)
This was applied to iproute2 net-next:
https://git.kernel.org/pub/scm/linux/kernel/git/dsahern/iproute2-next.git/
prev parent reply other threads:[~2017-12-25 22:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 2:01 [PATCH v4 iproute2 net-next] erspan: add erspan version II support William Tu
2017-12-25 22:44 ` David Ahern [this message]
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=1ac019fb-1a91-3664-affe-43a0d4a3502a@gmail.com \
--to=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=u9012063@gmail.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