On Fri 13 Jul 2018 at 03:54, Cong Wang wrote:
> On Sat, Jul 7, 2018 at 8:43 PM David Miller wrote:
>>
>> From: Vlad Buslov
>> Date: Thu, 5 Jul 2018 17:24:22 +0300
>>
>> > Currently, all netlink protocol handlers for updating rules, actions and
>> > qdiscs are protected with single global rtnl
On Sat, Jul 7, 2018 at 8:43 PM David Miller wrote:
>
> From: Vlad Buslov
> Date: Thu, 5 Jul 2018 17:24:22 +0300
>
> > Currently, all netlink protocol handlers for updating rules, actions and
> > qdiscs are protected with single global rtnl lock which removes any
> > possibility for parallelism.
From: Vlad Buslov
Date: Thu, 5 Jul 2018 17:24:22 +0300
> 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 first step to remove
> rtnl lock dependency f
From: Vlad Buslov
Date: Thu, 5 Jul 2018 17:24:22 +0300
> 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 first step to remove
> rtnl lock dependency f
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 first step to remove
rtnl lock dependency from TC rules update path.
Recently, new rtnl registration flag RT
