From: David Miller <davem@davemloft.net>
To: vladbu@mellanox.com
Cc: netdev@vger.kernel.org, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, jiri@resnulli.us, pablo@netfilter.org,
kadlec@blackhole.kfki.hu, fw@strlen.de, ast@kernel.org,
daniel@iogearbox.net, edumazet@google.com, keescook@chromium.org,
marcelo.leitner@gmail.com, kliteyn@mellanox.com
Subject: Re: [PATCH net-next v5 00/11] Modify action API for implementing lockless actions
Date: Mon, 04 Jun 2018 11:28:46 -0400 (EDT) [thread overview]
Message-ID: <20180604.112846.1169965769687697113.davem@davemloft.net> (raw)
In-Reply-To: <1527866118-21312-1-git-send-email-vladbu@mellanox.com>
From: Vlad Buslov <vladbu@mellanox.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.
prev parent reply other threads:[~2018-06-04 15:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 15:15 [PATCH net-next v5 00/11] Modify action API for implementing lockless actions Vlad Buslov
2018-06-01 15:15 ` [PATCH net-next v5 01/11] net: sched: use rcu for action cookie update Vlad Buslov
2018-06-01 15:15 ` [PATCH net-next v5 02/11] net: sched: change type of reference and bind counters Vlad Buslov
2018-06-01 15:15 ` [PATCH net-next v5 03/11] net: sched: implement unlocked action init API Vlad Buslov
2018-06-01 15:15 ` [PATCH net-next v5 04/11] net: sched: always take reference to action Vlad Buslov
2018-06-01 15:15 ` [PATCH net-next v5 05/11] net: sched: implement action API that deletes action by index Vlad Buslov
2018-06-01 15:15 ` [PATCH net-next v5 06/11] net: sched: add 'delete' function to action ops Vlad Buslov
2018-06-01 15:15 ` [PATCH net-next v5 07/11] net: sched: implement reference counted action release Vlad Buslov
2018-06-01 15:15 ` [PATCH net-next v5 08/11] net: sched: don't release reference on action overwrite Vlad Buslov
2018-06-01 15:15 ` [PATCH net-next v5 09/11] net: sched: use reference counting action init Vlad Buslov
2018-06-01 15:15 ` [PATCH net-next v5 10/11] net: sched: atomically check-allocate action Vlad Buslov
2018-06-01 15:15 ` [PATCH net-next v5 11/11] net: sched: change action API to use array of pointers to actions Vlad Buslov
2018-06-04 15:28 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180604.112846.1169965769687697113.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kadlec@blackhole.kfki.hu \
--cc=keescook@chromium.org \
--cc=kliteyn@mellanox.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=vladbu@mellanox.com \
--cc=xiyou.wangcong@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).