[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Za6k/o7BQvtijUJM@debian>
Date: Mon, 22 Jan 2024 18:25:18 +0100
From: Guillaume Nault <gnault@...hat.com>
To: Eric Dumazet <edumazet@...gle.com>
Cc: "David S . Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
David Ahern <dsahern@...nel.org>,
Kuniyuki Iwashima <kuniyu@...zon.com>,
Martin KaFai Lau <kafai@...com>, netdev@...r.kernel.org,
eric.dumazet@...il.com
Subject: Re: [PATCH net-next 6/9] sock_diag: allow concurrent operations
On Mon, Jan 22, 2024 at 11:26:00AM +0000, Eric Dumazet wrote:
> sock_diag_broadcast_destroy_work() and __sock_diag_cmd()
> are currently using sock_diag_table_mutex to protect
> against concurrent sock_diag_handlers[] changes.
>
> This makes inet_diag dump serialized, thus less scalable
> than legacy /proc files.
>
> It is time to switch to full RCU protection.
>
> Signed-off-by: Eric Dumazet <edumazet@...gle.com>
Reviewed-by: Guillaume Nault <gnault@...hat.com>
Powered by blists - more mailing lists