From: Jakub Kicinski <kuba@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>, <pabeni@redhat.com>,
<jiri@nvidia.com>
Subject: Re: [PATCH net-next v3 5/6] virtio_net: Add a lock for per queue RX coalesce
Date: Fri, 12 Apr 2024 19:21:11 -0700 [thread overview]
Message-ID: <20240412192111.7e0e1117@kernel.org> (raw)
In-Reply-To: <20240412195309.737781-6-danielj@nvidia.com>
On Fri, 12 Apr 2024 14:53:08 -0500 Daniel Jurgens wrote:
> Once the RTNL locking around the control buffer is removed there can be
> contention on the per queue RX interrupt coalescing data. Use a spin
> lock per queue.
Does not compile on Clang.
> + scoped_guard(spinlock, &vi->rq[i].intr_coal_lock) {
> + err = virtnet_send_rx_ctrl_coal_vq_cmd(vi, i,
> + vi->intr_coal_rx.max_usecs,
> + vi->intr_coal_rx.max_packets);
> + if (err)
> + return err;
> + }
Do you really think this needs a scoped guard and 4th indentation level,
instead of just:
..lock(..);
err = virtnet_send_rx_ctrl_coal_vq_cmd(vi, i,
vi->intr_coal_rx.max_usecs,
vi->intr_coal_rx.max_packets);
..unlock(..);
if (err)
return err;
> + scoped_guard(spinlock, &vi->rq[i].intr_coal_lock) {
> + vi->rq[i].intr_coal.max_usecs = ec->rx_coalesce_usecs;
> + vi->rq[i].intr_coal.max_packets = ec->rx_max_coalesced_frames;
> + }
:-|
--
pw-bot: cr
next prev parent reply other threads:[~2024-04-13 2:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 19:53 [PATCH net-next v3 0/6] Remove RTNL lock protection of CVQ Daniel Jurgens
2024-04-12 19:53 ` [PATCH net-next v3 1/6] virtio_net: Store RSS setting in virtnet_info Daniel Jurgens
2024-04-12 19:53 ` [PATCH net-next v3 2/6] virtio_net: Remove command data from control_buf Daniel Jurgens
2024-04-12 19:53 ` [PATCH net-next v3 3/6] virtio_net: Add a lock for the command VQ Daniel Jurgens
2024-04-12 19:53 ` [PATCH net-next v3 4/6] virtio_net: Do DIM update for specified queue only Daniel Jurgens
2024-04-12 19:53 ` [PATCH net-next v3 5/6] virtio_net: Add a lock for per queue RX coalesce Daniel Jurgens
2024-04-13 2:21 ` Jakub Kicinski [this message]
2024-04-16 3:15 ` Dan Jurgens
2024-04-16 14:27 ` Jakub Kicinski
2024-04-16 19:24 ` Dan Jurgens
2024-04-15 13:41 ` Heng Qi
2024-04-15 20:24 ` Dan Jurgens
2024-04-12 19:53 ` [PATCH net-next v3 6/6] virtio_net: Remove rtnl lock protection of command buffers Daniel Jurgens
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=20240412192111.7e0e1117@kernel.org \
--to=kuba@kernel.org \
--cc=danielj@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=jiri@nvidia.com \
--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).