[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <82caca13-7970-4f44-a68f-1efcf3e9a0f9@blackwall.org>
Date: Wed, 18 Jun 2025 18:13:44 +0300
From: Nikolay Aleksandrov <razor@...ckwall.org>
To: Stanislav Fomichev <stfomichev@...il.com>, netdev@...r.kernel.org
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, skalluru@...vell.com, manishc@...vell.com,
andrew+netdev@...n.ch, michael.chan@...adcom.com, pavan.chebbi@...adcom.com,
ajit.khaparde@...adcom.com, sriharsha.basavapatna@...adcom.com,
somnath.kotur@...adcom.com, anthony.l.nguyen@...el.com,
przemyslaw.kitszel@...el.com, tariqt@...dia.com, saeedm@...dia.com,
louis.peens@...igine.com, shshaikh@...vell.com,
GR-Linux-NIC-Dev@...vell.com, ecree.xilinx@...il.com, horms@...nel.org,
dsahern@...nel.org, shuah@...nel.org, tglx@...utronix.de, mingo@...nel.org,
ruanjinjie@...wei.com, idosch@...dia.com, petrm@...dia.com,
kuniyu@...gle.com, sdf@...ichev.me, linux-kernel@...r.kernel.org,
intel-wired-lan@...ts.osuosl.org, linux-rdma@...r.kernel.org,
oss-drivers@...igine.com, linux-net-drivers@....com,
linux-kselftest@...r.kernel.org, leon@...nel.org
Subject: Re: [PATCH net-next v5 2/6] vxlan: drop sock_lock
On 6/16/25 19:21, Stanislav Fomichev wrote:
> We won't be able to sleep soon in vxlan_offload_rx_ports and won't be
> able to grab sock_lock. Instead of having separate spinlock to
> manage sockets, rely on rtnl lock. This is similar to how geneve
> manages its sockets.
>
> Signed-off-by: Stanislav Fomichev <stfomichev@...il.com>
> ---
> drivers/net/vxlan/vxlan_core.c | 35 ++++++++++++-----------------
> drivers/net/vxlan/vxlan_private.h | 2 +-
> drivers/net/vxlan/vxlan_vnifilter.c | 18 ++++++---------
> 3 files changed, 22 insertions(+), 33 deletions(-)
>
Reviewed-by: Nikolay Aleksandrov <razor@...ckwall.org>
Powered by blists - more mailing lists