[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <23e442f0-a18b-4da0-9321-f543b028cd7e@linux.alibaba.com>
Date: Tue, 26 Mar 2024 10:54:20 +0800
From: Heng Qi <hengqi@...ux.alibaba.com>
To: Daniel Jurgens <danielj@...dia.com>, netdev@...r.kernel.org
Cc: mst@...hat.com, jasowang@...hat.com, xuanzhuo@...ux.alibaba.com,
virtualization@...ts.linux.dev, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, jiri@...dia.com
Subject: Re: [PATCH net-next 0/4] Remove RTNL lock protection of CVQ
在 2024/3/26 上午5:49, Daniel Jurgens 写道:
> Currently the buffer used for control VQ commands is protected by the
> RTNL lock. Previously this wasn't a major concern because the control
> VQ was only used during device setup and user interaction. With the
> recent addition of dynamic interrupt moderation the control VQ may be
> used frequently during normal operation.
>
> This series removes the RNTL lock dependancy by introducing a spin lock
> to protect the control buffer and writing SGs to the control VQ.
Hi Daniel.
It's a nice piece of work, but now that we're talking about ctrlq adding
interrupts, spin lock has some
conflicts with its goals. For example, we expect the ethtool command to
be blocked.
Therefore, a mutex lock may be more suitable.
Any how, the final conclusion may require some waiting.
Regards,
Heng
>
> Daniel Jurgens (4):
> virtio_net: Store RSS setting in virtnet_info
> virtio_net: Remove command data from control_buf
> virtio_net: Add a lock for the command VQ.
> virtio_net: Remove rtnl lock protection of command buffers
>
> drivers/net/virtio_net.c | 185 ++++++++++++++++++++++-----------------
> 1 file changed, 104 insertions(+), 81 deletions(-)
>
Powered by blists - more mailing lists