[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+HUmGhEVFaC1gGJiXK7N0hfiDf-4x3of3f54n2cbiDz+SnVZQ@mail.gmail.com>
Date: Thu, 17 Sep 2020 17:40:06 -0700
From: Francesco Ruggeri <fruggeri@...sta.com>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: open list <linux-kernel@...r.kernel.org>,
netdev <netdev@...r.kernel.org>,
Cong Wang <xiyou.wangcong@...il.com>,
Taehee Yoo <ap420073@...il.com>,
Andrii Nakryiko <andriin@...com>,
Eric Dumazet <edumazet@...gle.com>,
Jiri Pirko <jiri@...lanox.com>,
Alexei Starovoitov <ast@...nel.org>,
Jakub Kicinski <kuba@...nel.org>,
David Miller <davem@...emloft.net>
Subject: Re: [PATCH v3] net: use exponential backoff in netdev_wait_allrefs
On Thu, Sep 17, 2020 at 5:02 PM Stephen Hemminger
<stephen@...workplumber.org> wrote:
> Is there anyway to make RCU trigger faster?
This is a case of the networking code requiring multiple cascading grace periods
(functions executing at the end of a period scheduling more functions
for the end
of the next period), so it's a matter of how many steps are required,
rather than
how fast each step is, if that is what you are suggesting. I don't
think that expediting
rcu periods would help in this case, but I will defer to people with better
knowledge of the networking code than me to comment.
Powered by blists - more mailing lists