Re: [PATCH net-next v2 00/15] Remove rtnl lock dependency from all action implementations

2018-08-11 Thread David Miller
From: Vlad Buslov Date: Fri, 10 Aug 2018 20:51:40 +0300 > The goal of this change is to update specific actions APIs that access > action private state directly, in order to be independent from external > locking. General approach is to re-use existing tcf_lock spinlock (used > by some action

[PATCH net-next v2 00/15] Remove rtnl lock dependency from all action implementations

2018-08-10 Thread Vlad Buslov
Currently, all netlink protocol handlers for updating rules, actions and qdiscs are protected with single global rtnl lock which removes any possibility for parallelism. This patch set is a second step to remove rtnl lock dependency from TC rules update path. Recently, new rtnl registration flag