[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220208162148.285b5432@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Tue, 8 Feb 2022 16:21:48 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: "David S . Miller" <davem@...emloft.net>,
netdev <netdev@...r.kernel.org>,
Eric Dumazet <edumazet@...gle.com>,
Oliver Hartkopp <socketcan@...tkopp.net>,
Marc Kleine-Budde <mkl@...gutronix.de>,
linux-can@...r.kernel.org
Subject: Re: [PATCH net-next] can: gw: use call_rcu() instead of costly
synchronize_rcu()
On Mon, 7 Feb 2022 11:07:06 -0800 Eric Dumazet wrote:
> From: Eric Dumazet <edumazet@...gle.com>
>
> Commit fb8696ab14ad ("can: gw: synchronize rcu operations
> before removing gw job entry") added three synchronize_rcu() calls
> to make sure one rcu grace period was observed before freeing
> a "struct cgw_job" (which are tiny objects).
>
> This should be converted to call_rcu() to avoid adding delays
> in device / network dismantles.
>
> Use the rcu_head that was already in struct cgw_job,
> not yet used.
>
> Signed-off-by: Eric Dumazet <edumazet@...gle.com>
> Cc: Oliver Hartkopp <socketcan@...tkopp.net>
Adding Marc and linux-can to CC.
Powered by blists - more mailing lists