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,
stephen@networkplumber.org, ktkhai@virtuozzo.com,
nicolas.dichtel@6wind.com, gregkh@linuxfoundation.org,
mark.rutland@arm.com, leon@kernel.org,
paulmck@linux.vnet.ibm.com, fw@strlen.de, dsahern@gmail.com,
christian@brauner.io, lucien.xin@gmail.com,
jakub.kicinski@netronome.com, jbenc@redhat.com
Subject: Re: [PATCH net-next v3 00/10] Refactor classifier API to work with Qdisc/blocks without rtnl lock
Date: Tue, 25 Sep 2018 20:18:09 -0700 (PDT) [thread overview]
Message-ID: <20180925.201809.448916928209232352.davem@davemloft.net> (raw)
In-Reply-To: <1537805922-10744-1-git-send-email-vladbu@mellanox.com>
From: Vlad Buslov <vladbu@mellanox.com>
Date: Mon, 24 Sep 2018 19:18:32 +0300
...
> The goal of this change is to refactor tcf_block_find() and its
> dependencies to allow concurrent execution:
> - Extend Qdisc API with rcu to lookup and take reference to Qdisc
> without relying on rtnl lock.
> - Extend tcf_block with atomic reference counting and rcu.
> - Always take reference to tcf_block while working with it.
> - Implement tcf_block_release() to release resources obtained by
> tcf_block_find()
> - Create infrastructure to allow registering Qdiscs with class ops that
> do not require the caller to hold rtnl lock.
Series applied, thank you.
next prev parent reply other threads:[~2018-09-26 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 16:18 [PATCH net-next v3 00/10] Refactor classifier API to work with Qdisc/blocks without rtnl lock Vlad Buslov
2018-09-26 3:18 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-24 16:22 Vlad Buslov
2018-09-25 18:16 ` Cong Wang
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=20180925.201809.448916928209232352.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=christian@brauner.io \
--cc=dsahern@gmail.com \
--cc=fw@strlen.de \
--cc=gregkh@linuxfoundation.org \
--cc=jakub.kicinski@netronome.com \
--cc=jbenc@redhat.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=ktkhai@virtuozzo.com \
--cc=leon@kernel.org \
--cc=lucien.xin@gmail.com \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=stephen@networkplumber.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