From: Heng Qi <hengqi@linux.alibaba.com>
To: Daniel Jurgens <danielj@nvidia.com>
Cc: <mst@redhat.com>, <jasowang@redhat.com>,
<xuanzhuo@linux.alibaba.com>, <virtualization@lists.linux.dev>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <jiri@nvidia.com>,
Daniel Jurgens <danielj@nvidia.com>, <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v6 0/6] Remove RTNL lock protection of CVQ
Date: Mon, 6 May 2024 14:16:12 +0800 [thread overview]
Message-ID: <1714976172.0470116-1-hengqi@linux.alibaba.com> (raw)
In-Reply-To: <20240503202445.1415560-1-danielj@nvidia.com>
On Fri, 3 May 2024 23:24:39 +0300, Daniel Jurgens <danielj@nvidia.com> wrote:
> 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 dependency by introducing a mutex
> to protect the control buffer and writing SGs to the control VQ.
>
For the series, keep tags:
Reviewed-by: Heng Qi <hengqi@linux.alibaba.com>
Tested-by: Heng Qi <hengqi@linux.alibaba.com>
> v6:
> - Rebased over new stats code.
> - Added comment to cvq_lock, init the mutex unconditionally,
> and replaced some duplicate code with a goto.
> - Fixed minor grammer errors, checkpatch warnings, and clarified
> a comment.
> v5:
> - Changed cvq_lock to a mutex.
> - Changed dim_lock to mutex, because it's held taking
> the cvq_lock.
> - Use spin/mutex_lock/unlock vs guard macros.
> v4:
> - Protect dim_enabled with same lock as well intr_coal.
> - Rename intr_coal_lock to dim_lock.
> - Remove some scoped_guard where the error path doesn't
> have to be in the lock.
> v3:
> - Changed type of _offloads to __virtio16 to fix static
> analysis warning.
> - Moved a misplaced hunk to the correct patch.
> v2:
> - New patch to only process the provided queue in
> virtnet_dim_work
> - New patch to lock per queue rx coalescing structure.
>
> Daniel Jurgens (6):
> 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: Do DIM update for specified queue only
> virtio_net: Add a lock for per queue RX coalesce
> virtio_net: Remove rtnl lock protection of command buffers
>
> drivers/net/virtio_net.c | 288 +++++++++++++++++++++++----------------
> 1 file changed, 173 insertions(+), 115 deletions(-)
>
> --
> 2.44.0
>
>
next prev parent reply other threads:[~2024-05-06 6:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 20:24 [PATCH net-next v6 0/6] Remove RTNL lock protection of CVQ Daniel Jurgens
2024-05-03 20:24 ` [PATCH net-next v6 1/6] virtio_net: Store RSS setting in virtnet_info Daniel Jurgens
2024-05-03 20:24 ` [PATCH net-next v6 2/6] virtio_net: Remove command data from control_buf Daniel Jurgens
2024-05-15 12:44 ` Eric Dumazet
2024-05-15 13:27 ` Dan Jurgens
2024-05-03 20:24 ` [PATCH net-next v6 3/6] virtio_net: Add a lock for the command VQ Daniel Jurgens
2024-05-03 20:24 ` [PATCH net-next v6 4/6] virtio_net: Do DIM update for specified queue only Daniel Jurgens
2024-05-03 20:24 ` [PATCH net-next v6 5/6] virtio_net: Add a lock for per queue RX coalesce Daniel Jurgens
2024-05-03 20:24 ` [PATCH net-next v6 6/6] virtio_net: Remove rtnl lock protection of command buffers Daniel Jurgens
2024-05-06 6:16 ` Heng Qi [this message]
2024-05-07 6:29 ` [PATCH net-next v6 0/6] Remove RTNL lock protection of CVQ Jason Wang
2024-05-07 10:50 ` patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1714976172.0470116-1-hengqi@linux.alibaba.com \
--to=hengqi@linux.alibaba.com \
--cc=danielj@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).