From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id BE5F8A04DD; Wed, 21 Oct 2020 14:50:20 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id DF9FDAC62; Wed, 21 Oct 2020 14:50:17 +0200 (CEST) Received: from dispatch1-us1.ppe-hosted.com (dispatch1-us1.ppe-hosted.com [148.163.129.52]) by dpdk.org (Postfix) with ESMTP id DC09CAC60 for ; Wed, 21 Oct 2020 14:50:14 +0200 (CEST) Received: from mx1-us1.ppe-hosted.com (unknown [10.7.65.64]) by dispatch1-us1.ppe-hosted.com (PPE Hosted ESMTP Server) with ESMTP id 249D96006A; Wed, 21 Oct 2020 12:50:13 +0000 (UTC) Received: from us4-mdac16-26.ut7.mdlocal (unknown [10.7.66.46]) by mx1-us1.ppe-hosted.com (PPE Hosted ESMTP Server) with ESMTP id 2264D200A4; Wed, 21 Oct 2020 12:50:13 +0000 (UTC) X-Virus-Scanned: Proofpoint Essentials engine Received: from mx1-us1.ppe-hosted.com (unknown [10.7.66.40]) by mx1-us1.ppe-hosted.com (PPE Hosted ESMTP Server) with ESMTPS id 98CC022005B; Wed, 21 Oct 2020 12:50:12 +0000 (UTC) Received: from webmail.solarflare.com (uk.solarflare.com [193.34.186.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mx1-us1.ppe-hosted.com (PPE Hosted ESMTP Server) with ESMTPS id 2011BBC006B; Wed, 21 Oct 2020 12:50:12 +0000 (UTC) Received: from [127.0.0.27] (10.17.10.39) by ukex01.SolarFlarecom.com (10.17.10.4) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 21 Oct 2020 13:50:05 +0100 To: Ferruh Yigit , References: <1603183709-23420-1-git-send-email-arybchenko@solarflare.com> <1603185222-14831-1-git-send-email-arybchenko@solarflare.com> <21ca5a91-68c8-d512-9bb6-7361be182b05@intel.com> From: Andrew Rybchenko Message-ID: <07981ba6-450e-d674-a067-58b857454e2d@solarflare.com> Date: Wed, 21 Oct 2020 15:49:43 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.3.1 MIME-Version: 1.0 In-Reply-To: <21ca5a91-68c8-d512-9bb6-7361be182b05@intel.com> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Originating-IP: [10.17.10.39] X-ClientProxiedBy: ocex03.SolarFlarecom.com (10.20.40.36) To ukex01.SolarFlarecom.com (10.17.10.4) X-TM-AS-Product-Ver: SMEX-12.5.0.1300-8.6.1012-25738.003 X-TM-AS-Result: No-4.419100-8.000000-10 X-TMASE-MatchedRID: gzVbiXtWD9uNGiB3p54P+vZvT2zYoYOwC/ExpXrHizyGjDxbChb90OIO L9oaYI3+V5+/E1K+33g6ucMiowSQ+SlfBzClEKcgIDrhNaNLPjq3xwqfnvnKHsAkyHiYDAQbZEE GRcR44i50eDC4UVkt+9f/Zlv5FLosH8RVhpQ01d4HK0IhbYfex5iv+7AdcXdSYy6fApvL8Be8T+ 8Su0DvO/d6MRSDtSymim9L9cxrfGHLT+zT3jlQ6SknxKlVP07/1JP9NndNOkVjHRW0GpKiDQ2o6 ebnCAbgf9iDS1Cmt3AUH8PmWo2hhRTBVEIvqWphiJwEp8weVXzihJ3Xxt2bAjbpMgyAfh26qr3Q aOfXLr271Lj6Et7AQYodqzyCX/xz3drJ6tQCW5414ETxvAKbskX+NKU+2Zr+4Vo4xoaXBy/+ezf og1uF0z1u8tWI900nHlNfm/7/9HTtFyyh43HpLKJVTu7sjgg1vz4HH9cCDtnfc2Xd6VJ+yhSNCC rV6iq2585VzGMOFzABi3kqJOK62QtuKBGekqUpnH7sbImOEBT0/0wGbeHO49+DL7kflqq9mTekD 1S3VWHu4hqzvuF3VLbD5pp68TKEdTnLe/fFt9juy+NLkTQ0xJlv1BD3V6WS7pTw7qBEYgmPgCDb AY3P7tVH8LonOSWy/S2A05ietQe2WKPzVcog4R/BXqwE9HSW X-TM-AS-User-Approved-Sender: Yes X-TM-AS-User-Blocked-Sender: No X-TMASE-Result: 10--4.419100-8.000000 X-TMASE-Version: SMEX-12.5.0.1300-8.6.1012-25738.003 X-MDID: 1603284613-VFo4dPzgUpJ7 X-PPE-DISP: 1603284613;VFo4dPzgUpJ7 Subject: Re: [dpdk-dev] [PATCH v2 00/62] net/sfc: support flow API transfer rules X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 10/21/20 2:13 PM, Ferruh Yigit wrote: > On 10/20/2020 10:12 AM, Andrew Rybchenko wrote: >> Transfer rules for Alveo SN1000 SmartNICs support matching on various >> inner and outer packet headers, traffic source items like PORT_ID, >> PHY_PORT, PF and VF and actions to route traffic to destination >> (PORT_ID, PHY_PORT, PF, VF or DROP), MARK, FLAG and apply VLAN >> push/pop transformations. >> >> >> Andrew Rybchenko (2): >>    common/sfc_efx/base: add MAE definitions to MCDI >>    doc: advertise flow API transfer rules support in net/sfc >> >> Ivan Malov (60): >>    common/sfc_efx/base: indicate support for MAE >>    net/sfc: add a stub for attaching to MAE >>    common/sfc_efx/base: add MAE init/fini APIs >>    drivers: init/fini MAE on attach/detach >>    common/sfc_efx/base: add an MAE limit query API >>    net/sfc: add the concept of MAE (transfer) rules >>    common/sfc_efx/base: add match spec init/fini APIs >>    net/sfc: add pattern parsing stub to MAE backend >>    common/sfc_efx/base: add a match spec validate API >>    net/sfc: validate match spec in MAE backend >>    common/sfc_efx/base: add a match specs class comparison API >>    net/sfc: add verify method to flow validate path >>    common/sfc_efx/base: add action set spec init/fini APIs >>    net/sfc: add actions parsing stub to MAE backend >>    common/sfc_efx/base: support setting a PPORT in a match spec >>    net/sfc: support flow item PHY PORT in MAE backend >>    common/sfc_efx/base: add MAE match fields for Ethernet >>    net/sfc: support flow item ETH in MAE backend >>    common/sfc_efx/base: support adding DELIVER action to a set >>    net/sfc: support flow action PHY PORT in MAE backend >>    common/sfc_efx/base: add MAE action set provisioning APIs >>    common/sfc_efx/base: add MAE action rule provisioning APIs >>    net/sfc: implement flow insert/remove in MAE backend >>    common/sfc_efx/base: support adding VLAN POP action to a set >>    net/sfc: support flow action OF POP VLAN in MAE backend >>    common/sfc_efx/base: support adding VLAN PUSH action >>    net/sfc: add facilities to handle bundles of actions >>    net/sfc: support VLAN PUSH actions in MAE backend >>    common/sfc_efx/base: support adding FLAG action to a set >>    net/sfc: support flow action FLAG in MAE backend >>    common/sfc_efx/base: support adding MARK action to a set >>    net/sfc: support flow action MARK in MAE backend >>    common/sfc_efx/base: add named constant for invalid VF >>    common/sfc_efx/base: add an API to get MPORT of a PF/VF >>    net/sfc: support flow items PF and VF in transfer rules >>    net/sfc: support flow actions PF and VF in transfer rules >>    common/sfc_efx/base: add an API for adding action DROP >>    net/sfc: support flow action DROP in transfer rules >>    common/sfc_efx/base: refactor version / boot info get helper >>    common/sfc_efx/base: add an API for querying board info >>    net/sfc: add HW switch ID helpers >>    net/sfc: support the concept of RTE switch domains/ports >>    net/sfc: support flow action PORT ID in transfer rules >>    net/sfc: support flow item PORT ID in transfer rules >>    common/sfc_efx/base: add MAE match fields for VLAN >>    net/sfc: support flow item VLAN in transfer rules >>    common/sfc_efx/base: add MAE match fields for IPv4 >>    net/sfc: support flow item IPV4 in transfer rules >>    common/sfc_efx/base: add MAE match fields for IPv6 >>    net/sfc: support flow item IPV6 in transfer rules >>    common/sfc_efx/base: add MAE match fields for TCP and UDP >>    net/sfc: support flow item TCP in transfer rules >>    net/sfc: support flow item UDP in transfer rules >>    common/sfc_efx/base: indicate MAE support for encapsulation >>    common/sfc_efx/base: add MAE encap. match fields >>    common/sfc_efx/base: add MAE match field VNET ID for tunnels >>    common/sfc_efx/base: add an API to compare match specs >>    common/sfc_efx/base: validate and compare outer match specs >>    common/sfc_efx/base: support outer rule provisioning >>    net/sfc: support encap. flow items in transfer rules > > Series applied to dpdk-next-net/main, thanks. > > (Some of the commit logs were longer than 72 chars that I am trying to > limit, but I didn't dare to break Ivan's perfect alignment, so I let > them be.) Thanks, I'm wondering why check-git-log.sh does not complain on it.