From: Vlad Buslov <vladbu@nvidia.com>
To: Pedro Tammela <pctammela@mojatatu.com>
Cc: <netdev@vger.kernel.org>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<jhs@mojatatu.com>, <xiyou.wangcong@gmail.com>,
<jiri@resnulli.us>, <marcelo.leitner@gmail.com>
Subject: Re: [PATCH net-next v2 0/2] net/sched: optimizations around action binding and init
Date: Tue, 12 Dec 2023 19:34:44 +0200 [thread overview]
Message-ID: <874jgn727z.fsf@nvidia.com> (raw)
In-Reply-To: <20231211181807.96028-1-pctammela@mojatatu.com>
On Mon 11 Dec 2023 at 15:18, Pedro Tammela <pctammela@mojatatu.com> wrote:
> Scaling optimizations for action binding in rtnl-less filters.
> We saw a noticeable lock contention around idrinfo->lock when
> testing in a 56 core system, which disappeared after the patches.
>
> v1->v2:
> - Address comments from Vlad
>
> Pedro Tammela (2):
> net/sched: act_api: rely on rcu in tcf_idr_check_alloc
> net/sched: act_api: skip idr replace on bound actions
Reviewed-by: Vlad Buslov <vladbu@nvidia.com>
[...]
next prev parent reply other threads:[~2023-12-12 17:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 18:18 [PATCH net-next v2 0/2] net/sched: optimizations around action binding and init Pedro Tammela
2023-12-11 18:18 ` [PATCH net-next v2 1/2] net/sched: act_api: rely on rcu in tcf_idr_check_alloc Pedro Tammela
2023-12-11 18:18 ` [PATCH net-next v2 2/2] net/sched: act_api: skip idr replace on bound actions Pedro Tammela
2023-12-12 15:59 ` [PATCH net-next v2 0/2] net/sched: optimizations around action binding and init Jamal Hadi Salim
2023-12-12 17:34 ` Vlad Buslov [this message]
2023-12-14 2:00 ` patchwork-bot+netdevbpf
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=874jgn727z.fsf@nvidia.com \
--to=vladbu@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.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).