Re: [PATCH 00/12 net-next,v7] add flow_rule infrastructure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2/6/19 10:39 AM, David Miller wrote:
> From: Pablo Neira Ayuso <pablo@xxxxxxxxxxxxx>
> Date: Sat,  2 Feb 2019 12:50:42 +0100
> 
>> This patchset, as is, allows us to reuse the driver codebase to
>> configure ACL hardware offloads for the ethtool_rxnfc and the TC flower
>> interfaces. A few clients for this infrastructure are presented, such as
>> the bcm_sf2 and the qede drivers, for reference. Moreover all of the
>> existing drivers in the tree are converted to use this infrastructure.
>>
>> This patchset is re-using the existing flow dissector infrastructure
>> that was introduced by Jiri Pirko et al. so the amount of abstractions
>> that this patchset adds are minimal. Well, just a few wrapper structures
>> for the selector side of the rules. And, in order to express actions,
>> this patchset exposes an action API that is based on the existing TC
>> action infrastructure and what existing drivers already support on that
>> front.
>>
>> v7: This patchset is a rebase on top of the net-next tree, after
>>     addressing questions and feedback from driver developers in the
>>     last batch.
> 
> Ok, I've thought long and hard about this.
> 
> Applied to net-next, let's see where this goes.
> 
> I'll push this out after my build testing completes.

Great! Thanks. FWIW, I just ran basic testing on bcm_sf2 with this
series applied and have not had regressions, so this is good.
-- 
Florian



[Index of Archives]     [Netfitler Users]     [LARTC]     [Bugtraq]     [Yosemite Forum]

  Powered by Linux