From: Stephen Hemminger <stephen@networkplumber.org>
To: fruggeri@arista.com (Francesco Ruggeri)
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
xiyou.wangcong@gmail.com, ap420073@gmail.com, andriin@fb.com,
edumazet@google.com, jiri@mellanox.com, ast@kernel.org,
kuba@kernel.org, davem@davemloft.net
Subject: Re: [PATCH v3] net: use exponential backoff in netdev_wait_allrefs
Date: Thu, 17 Sep 2020 17:02:03 -0700 [thread overview]
Message-ID: <20200917170203.1a363082@hermes.lan> (raw)
In-Reply-To: <20200917234953.CB1D295C0A69@us180.sjc.aristanetworks.com>
On Thu, 17 Sep 2020 16:49:53 -0700
fruggeri@arista.com (Francesco Ruggeri) wrote:
> The combination of aca_free_rcu, introduced in commit 2384d02520ff
> ("net/ipv6: Add anycast addresses to a global hashtable"), and
> fib6_info_destroy_rcu, introduced in commit 9b0a8da8c4c6 ("net/ipv6:
> respect rcu grace period before freeing fib6_info"), can result in
> an extra rcu grace period being needed when deleting an interface,
> with the result that netdev_wait_allrefs ends up hitting the msleep(250),
> which is considerably longer than the required grace period.
> This can result in long delays when deleting a large number of interfaces,
> and it can be observed with this script:
>
Is there anyway to make RCU trigger faster?
next prev parent reply other threads:[~2020-09-18 0:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 23:49 [PATCH v3] net: use exponential backoff in netdev_wait_allrefs Francesco Ruggeri
2020-09-18 0:02 ` Stephen Hemminger [this message]
2020-09-18 0:40 ` Francesco Ruggeri
2020-09-18 8:48 ` Eric Dumazet
2020-09-18 9:00 ` Eric Dumazet
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=20200917170203.1a363082@hermes.lan \
--to=stephen@networkplumber.org \
--cc=andriin@fb.com \
--cc=ap420073@gmail.com \
--cc=ast@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fruggeri@arista.com \
--cc=jiri@mellanox.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.