[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20180604.112846.1169965769687697113.davem@davemloft.net>
Date: Mon, 04 Jun 2018 11:28:46 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: vladbu@...lanox.com
Cc: netdev@...r.kernel.org, jhs@...atatu.com, xiyou.wangcong@...il.com,
jiri@...nulli.us, pablo@...filter.org, kadlec@...ckhole.kfki.hu,
fw@...len.de, ast@...nel.org, daniel@...earbox.net,
edumazet@...gle.com, keescook@...omium.org,
marcelo.leitner@...il.com, kliteyn@...lanox.com
Subject: Re: [PATCH net-next v5 00/11] Modify action API for implementing
lockless actions
From: Vlad Buslov <vladbu@...lanox.com>
Date: Fri, 1 Jun 2018 18:15:07 +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 from TC rules update path.
Hello Vlad.
I've read over this patch series a few times, and even though I can't
find any issues yet, I think this series is complex and invasive
enough that it should receive more time for review by other experts.
Therefore I'm deferring this to the next merge window in order to
accomodate that.
Thank you.
Powered by blists - more mailing lists