[dpdk-dev] [PATCH v2 00/62] net/sfc: support flow API transfer rules

[Andrew Rybchenko]

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.