From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 1A7921B3B9; Wed, 6 Feb 2019 12:00:48 +0100 (CET) Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 20DB688302; Wed, 6 Feb 2019 11:00:47 +0000 (UTC) Received: from ktraynor.remote.csb (unknown [10.33.36.135]) by smtp.corp.redhat.com (Postfix) with ESMTP id 16E2210DF1C1; Wed, 6 Feb 2019 11:00:44 +0000 (UTC) To: Slava Ovsiienko , Shahaf Shuler Cc: "dev@dpdk.org" , "stable@dpdk.org" , Thomas Monjalon , Yongseok Koh , Luca Boccassi , "stable@dpdk.org" References: <1545924885-6215-1-git-send-email-viacheslavo@mellanox.com> <590129bf-3012-25bf-bac5-fedf1c705a25@redhat.com> From: Kevin Traynor Organization: Red Hat Message-ID: <84256b9d-c183-4f9e-2f28-2ee6ad428032@redhat.com> Date: Wed, 6 Feb 2019 11:00:44 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.28]); Wed, 06 Feb 2019 11:00:47 +0000 (UTC) Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH 0/5] net/mlx5: add inner tunnel items support on E-Switch X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Feb 2019 11:00:48 -0000 On 01/31/2019 04:13 PM, Slava Ovsiienko wrote: > Hi, Kevin > Hi Slava, > It is rather refactoring, not new feature, tunnel inner items support is partially present in 18.11. > Yes, this patchset is too big to be simple fix, and updates not so much to be new feature. > It is very early patch (after 18.11 release), just mailed later, rebase on the top was done > automatically and quite simple, because it touches merely E-Switch subsystem (merge should > not be difficult - mostly mlx5_flow_tcf.c is changed) and highly desirable to be backported. > It fixes serious bugs with ether_type field, which limit VLAN and VXLAN functionality on E-Switch. > The issue I have is it also adding functionality and more importantly reworking how some existing behavior is handled (e.g. outer tunnel validation moving in 1/5). But, yes, it is completely isolated to mlx5/tcf and applies cleanly, so that is a positive. As it's a bit grey, I will backport to 18.11 on the understanding that it will be supported by Mellanox and you will test one of the 18.11.1-RC's to make sure there are no regressions on the existing behavior - is that reasonable? thanks, Kevin. > With best regards, > Slava (aka Viacheslav) > >> -----Original Message----- >> From: Kevin Traynor >> Sent: Thursday, January 31, 2019 16:52 >> To: Slava Ovsiienko ; Shahaf Shuler >> >> Cc: dev@dpdk.org; stable@dpdk.org; Thomas Monjalon >> ; Yongseok Koh ; Luca >> Boccassi >> Subject: Re: [dpdk-dev] [PATCH 0/5] net/mlx5: add inner tunnel items support >> on E-Switch >> >> On 12/27/2018 03:34 PM, Viacheslav Ovsiienko wrote: >>> The generic Flow rule for tunnels looks like: >>> >>> flow create \ >>> \ >>> \ >>> >>> >>> 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 >> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdoc.dp >> dk.org%2Fguides%2Fcontributing%2Fstable.html%23what-changes-should-be- >> backported&data=02%7C01%7Cviacheslavo%40mellanox.com%7C1d6e08 >> fe6f7f47d83f7e08d6878bb56d%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0 >> %7C0%7C636845431441557730&sdata=%2Fmgoj2Il%2Fu4CCrkAcETdoMp >> d7Ri5ash%2FUhzGv1dLXLY%3D&reserved=0 >> >> -- >> 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 >>> >>> 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(-) >>> >