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: sta...@dpdk.org >
Hi Viacheslav - these are new features, not a bugfixes. Are the sta...@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 <viachesl...@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(-) >
