[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Za6euh/VzIiyU1Nw@debian>
Date: Mon, 22 Jan 2024 17:58:34 +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 4/9] inet_diag: allow concurrent operations
On Mon, Jan 22, 2024 at 11:25:58AM +0000, Eric Dumazet wrote:
> inet_diag_lock_handler() current implementation uses a mutex
> to protect inet_diag_table[] array against concurrent changes.
>
> This makes inet_diag dump serialized, thus less scalable
> than legacy /proc files.
>
> It is time to switch to full RCU protection.
>
> As a bonus, if a target is statically linked instead of being
> modular, inet_diag_lock_handler() & inet_diag_unlock_handler()
> reduce to reads only.
>
> Signed-off-by: Eric Dumazet <edumazet@...gle.com>
Reviewed-by: Guillaume Nault <gnault@...hat.com>
Powered by blists - more mailing lists