From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Jurgens <danielj@nvidia.com>
Cc: netdev@vger.kernel.org, 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
Subject: Re: [PATCH net-next v6 0/6] Remove RTNL lock protection of CVQ
Date: Tue, 07 May 2024 10:50:27 +0000 [thread overview]
Message-ID: <171507902730.3484.10843035496334670534.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240503202445.1415560-1-danielj@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 3 May 2024 23:24:39 +0300 you 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.
>
> [...]
Here is the summary with links:
- [net-next,v6,1/6] virtio_net: Store RSS setting in virtnet_info
https://git.kernel.org/netdev/net-next/c/fce29030c565
- [net-next,v6,2/6] virtio_net: Remove command data from control_buf
https://git.kernel.org/netdev/net-next/c/ff7c7d9f5261
- [net-next,v6,3/6] virtio_net: Add a lock for the command VQ.
https://git.kernel.org/netdev/net-next/c/6f45ab3e0409
- [net-next,v6,4/6] virtio_net: Do DIM update for specified queue only
https://git.kernel.org/netdev/net-next/c/650d77c51e24
- [net-next,v6,5/6] virtio_net: Add a lock for per queue RX coalesce
https://git.kernel.org/netdev/net-next/c/4d4ac2ececd3
- [net-next,v6,6/6] virtio_net: Remove rtnl lock protection of command buffers
https://git.kernel.org/netdev/net-next/c/f8befdb21be0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-05-07 10:50 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 ` [PATCH net-next v6 0/6] Remove RTNL lock protection of CVQ Heng Qi
2024-05-07 6:29 ` Jason Wang
2024-05-07 10:50 ` patchwork-bot+netdevbpf [this message]
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=171507902730.3484.10843035496334670534.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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).