From: Kevin Traynor <ktraynor@redhat.com>
To: Viacheslav Ovsiienko <viacheslavo@mellanox.com>, shahafs@mellanox.com
Cc: dev@dpdk.org, stable@dpdk.org,
Thomas Monjalon <thomas@monjalon.net>,
Yongseok Koh <yskoh@mellanox.com>,
Luca Boccassi <bluca@debian.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH 0/5] net/mlx5: add inner tunnel items support on E-Switch
Date: Thu, 31 Jan 2019 14:52:17 +0000 [thread overview]
Message-ID: <590129bf-3012-25bf-bac5-fedf1c705a25@redhat.com> (raw)
In-Reply-To: <1545924885-6215-1-git-send-email-viacheslavo@mellanox.com>
On 12/27/2018 03:34 PM, Viacheslav Ovsiienko wrote:
> The generic Flow rule for tunnels looks like:
>
> flow create <attributes> <port> \
> <tunnel outer items pattern> \
> <tunnel vni item> \
> <tunnel inner items pattern>
>
> Current design supports only L2 addresses as inner pattern
> items. This patchset adds support for L3 (IPv4/IPv6) addresses
> and L4 (TCP/UDP) ports items as inner tunnel parameters.
>
> Also this patchset adds support for inner and outer ethernet
> types for the E-Switch Flows with tunnels. Inner and outer ethernet
> type match can be specified with ethernet items, vlan items, or
> implicitly deduced from IP address items. The tcm_info field
> in Netlink message tcm structure is filled always with outer
> protocol.
>
> Cc: stable@dpdk.org
>
Hi Viacheslav - these are new features, not a bugfixes. Are the
stable@dpdk.org tags intentional?
From
http://doc.dpdk.org/guides/contributing/stable.html#what-changes-should-be-backported
--
Features should not be backported to stable releases. It may be
acceptable, in limited cases, to back port features for the LTS release
where:
There is a justifiable use case (for example a new PMD).
The change is non-invasive.
The work of preparing the backport is done by the proposer.
There is support within the community.
--
Kevin.
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
>
> Viacheslav Ovsiienko (5):
> net/mlx5: remove checks for outer tunnel items on E-Switch
> net/mlx5: add tunnel inner items validation on E-Switch
> net/mlx5: add tunnel inner items support on E-Switch
> net/mlx5: add ethernet type validation on E-Switch
> net/mlx5: add ethernet type support for tunnels on E-Switch
>
> drivers/net/mlx5/mlx5_flow_tcf.c | 690 ++++++++++++++++++++++-----------------
> 1 file changed, 399 insertions(+), 291 deletions(-)
>
next prev parent reply other threads:[~2019-01-31 14:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-27 15:34 [dpdk-stable] " Viacheslav Ovsiienko
2018-12-27 15:34 ` [dpdk-stable] [PATCH 1/5] net/mlx5: remove checks for outer tunnel items " Viacheslav Ovsiienko
2018-12-27 15:34 ` [dpdk-stable] [PATCH 2/5] net/mlx5: add tunnel inner items validation " Viacheslav Ovsiienko
2018-12-27 15:34 ` [dpdk-stable] [PATCH 3/5] net/mlx5: add tunnel inner items support " Viacheslav Ovsiienko
2018-12-27 15:34 ` [dpdk-stable] [PATCH 4/5] net/mlx5: add ethernet type validation " Viacheslav Ovsiienko
2018-12-27 15:34 ` [dpdk-stable] [PATCH 5/5] net/mlx5: add ethernet type support for tunnels " Viacheslav Ovsiienko
2019-01-13 12:11 ` [dpdk-stable] [dpdk-dev] [PATCH 0/5] net/mlx5: add inner tunnel items support " Shahaf Shuler
2019-01-31 14:52 ` Kevin Traynor [this message]
2019-01-31 16:13 ` Slava Ovsiienko
2019-02-06 11:00 ` Kevin Traynor
2019-02-06 11:56 ` Slava Ovsiienko
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=590129bf-3012-25bf-bac5-fedf1c705a25@redhat.com \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=shahafs@mellanox.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=viacheslavo@mellanox.com \
--cc=yskoh@mellanox.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;
as well as URLs for NNTP newsgroup(s).