From: "Michael S. Tsirkin" <mst@redhat.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: xuanzhuo@linux.alibaba.com, linux-kernel@vger.kernel.org,
hawk@kernel.org, daniel@iogearbox.net, netdev@vger.kernel.org,
john.fastabend@gmail.com, ast@kernel.org, gavi@nvidia.com,
edumazet@google.com, Heng Qi <hengqi@linux.alibaba.com>,
jiri@nvidia.com, kuba@kernel.org, bpf@vger.kernel.org,
virtualization@lists.linux-foundation.org, davem@davemloft.net,
Gavin Li <gavinl@nvidia.com>
Subject: Re: [PATCH net-next V4 2/3] virtio_net: support per queue interrupt coalesce command
Date: Fri, 28 Jul 2023 01:46:23 -0400 [thread overview]
Message-ID: <20230728014601-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <f5823996fffad2f3c1862917772c182df74c74e7.camel@redhat.com>
On Thu, Jul 27, 2023 at 03:28:32PM +0200, Paolo Abeni wrote:
> On Tue, 2023-07-25 at 16:07 +0300, Gavin Li wrote:
> > Add interrupt_coalesce config in send_queue and receive_queue to cache user
> > config.
> >
> > Send per virtqueue interrupt moderation config to underlying device in
> > order to have more efficient interrupt moderation and cpu utilization of
> > guest VM.
> >
> > Additionally, address all the VQs when updating the global configuration,
> > as now the individual VQs configuration can diverge from the global
> > configuration.
> >
> > Signed-off-by: Gavin Li <gavinl@nvidia.com>
> > Reviewed-by: Dragos Tatulea <dtatulea@nvidia.com>
> > Reviewed-by: Jiri Pirko <jiri@nvidia.com>
> > Acked-by: Michael S. Tsirkin <mst@redhat.com>
>
> FTR, this patch is significantly different from the version previously
> acked/reviewed, I'm unsure if all the reviewers are ok with the new
> one.
>
> [...]
still ok by me
Acked-by: Michael S. Tsirkin <mst@redhat.com>
let's wait for Jason too.
> > static int virtnet_set_coalesce(struct net_device *dev,
> > struct ethtool_coalesce *ec,
> > struct kernel_ethtool_coalesce *kernel_coal,
> > struct netlink_ext_ack *extack)
> > {
> > struct virtnet_info *vi = netdev_priv(dev);
> > - int ret, i, napi_weight;
> > + int ret, queue_number, napi_weight;
> > bool update_napi = false;
> >
> > /* Can't change NAPI weight if the link is up */
> > napi_weight = ec->tx_max_coalesced_frames ? NAPI_POLL_WEIGHT : 0;
> > - if (napi_weight ^ vi->sq[0].napi.weight) {
> > - if (dev->flags & IFF_UP)
> > - return -EBUSY;
> > - else
> > - update_napi = true;
> > + for (queue_number = 0; queue_number < vi->max_queue_pairs; queue_number++) {
> > + ret = virtnet_should_update_vq_weight(dev->flags, napi_weight,
> > + vi->sq[queue_number].napi.weight,
> > + &update_napi);
> > + if (ret)
> > + return ret;
> > +
> > + if (update_napi) {
> > + /* All queues that belong to [queue_number, queue_count] will be
> > + * updated for the sake of simplicity, which might not be necessary
>
> It looks like the comment above still refers to the old code. Should
> be:
> [queue_number, vi->max_queue_pairs]
>
> Otherwise LGTM, thanks!
>
> Paolo
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2023-07-28 5:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230725130709.58207-1-gavinl@nvidia.com>
[not found] ` <20230725130709.58207-3-gavinl@nvidia.com>
2023-07-27 13:28 ` [PATCH net-next V4 2/3] virtio_net: support per queue interrupt coalesce command Paolo Abeni
2023-07-28 1:42 ` Jason Wang
2023-07-28 5:46 ` Michael S. Tsirkin [this message]
2023-07-31 6:25 ` Jason Wang
2023-07-31 6:24 ` Jason Wang
[not found] ` <20230725130709.58207-4-gavinl@nvidia.com>
2023-07-31 6:24 ` [PATCH net-next V4 3/3] virtio_net: enable per queue interrupt coalesce feature Jason Wang
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=20230728014601-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gavi@nvidia.com \
--cc=gavinl@nvidia.com \
--cc=hawk@kernel.org \
--cc=hengqi@linux.alibaba.com \
--cc=jiri@nvidia.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--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).