From: Heng Qi <hengqi@linux.alibaba.com>
To: Jason Wang <jasowang@redhat.com>
Cc: netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org,
"Michael S . Tsirkin" <mst@redhat.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Jesper Dangaard Brouer <hawk@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
Gavin Li <gavinl@nvidia.com>
Subject: Re: [PATCH net 5/6] virtio-net: fix the vq coalescing setting for vq resize
Date: Fri, 22 Sep 2023 15:58:40 +0800 [thread overview]
Message-ID: <2ffd0e15-107e-4c46-8d98-caf47ff6a0c6@linux.alibaba.com> (raw)
In-Reply-To: <CACGkMEv4me_mjRJ8wEd-w_b9tjo370d6idioCTmFwJo-3TH3-A@mail.gmail.com>
在 2023/9/22 下午3:32, Jason Wang 写道:
> On Fri, Sep 22, 2023 at 1:02 PM Heng Qi <hengqi@linux.alibaba.com> wrote:
>>
>>
>> 在 2023/9/22 下午12:29, Jason Wang 写道:
>>> On Tue, Sep 19, 2023 at 3:49 PM Heng Qi <hengqi@linux.alibaba.com> wrote:
>>>> According to the definition of virtqueue coalescing spec[1]:
>>>>
>>>> Upon disabling and re-enabling a transmit virtqueue, the device MUST set
>>>> the coalescing parameters of the virtqueue to those configured through the
>>>> VIRTIO_NET_CTRL_NOTF_COAL_TX_SET command, or, if the driver did not set
>>>> any TX coalescing parameters, to 0.
>>>>
>>>> Upon disabling and re-enabling a receive virtqueue, the device MUST set
>>>> the coalescing parameters of the virtqueue to those configured through the
>>>> VIRTIO_NET_CTRL_NOTF_COAL_RX_SET command, or, if the driver did not set
>>>> any RX coalescing parameters, to 0.
>>>>
>>>> We need to add this setting for vq resize (ethtool -G) where vq_reset happens.
>>>>
>>>> [1] https://lists.oasis-open.org/archives/virtio-dev/202303/msg00415.html
>>>>
>>>> Fixes: 394bd87764b6 ("virtio_net: support per queue interrupt coalesce command")
>>> I'm not sure this is a real fix as spec allows it to go zero?
>> The spec says that if the user has configured interrupt coalescing
>> parameters,
>> parameters need to be restored after vq_reset, otherwise set to 0.
>> vi->intr_coal_tx and vi->intr_coal_rx always save the newest global
>> parameters,
>> regardless of whether the command is sent or not. So I think we need
>> this patch
>> it complies with the specification requirements.
> How can we make sure the old coalescing parameters still make sense
> for the new ring size?
I'm not sure, ringsize has a wider range of changes. Maybe we should
only keep coalescing
parameters in cases where only vq_reset occurs (no ring size change
involved)?
Thanks!
>
> Thanks
>
>> Thanks!
>>
>>> Thanks
next prev parent reply other threads:[~2023-09-22 7:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 7:49 [PATCH net 0/6] virtio-net: Fix and update interrupt moderation Heng Qi
2023-09-19 7:49 ` [PATCH net 1/6] virtio-net: initially change the value of tx-frames Heng Qi
2023-09-21 7:03 ` Jason Wang
2023-09-19 7:49 ` [PATCH net 2/6] virtio-net: fix mismatch of getting tx-frames Heng Qi
2023-09-22 3:11 ` Jason Wang
2023-09-19 7:49 ` [PATCH net 3/6] virtio-net: consistently save parameters for per-queue Heng Qi
2023-09-22 4:26 ` Jason Wang
2023-09-19 7:49 ` [PATCH net 4/6] virtio-net: fix per queue coalescing parameter setting Heng Qi
2023-09-22 4:27 ` Jason Wang
2023-09-19 7:49 ` [PATCH net 5/6] virtio-net: fix the vq coalescing setting for vq resize Heng Qi
2023-09-22 4:29 ` Jason Wang
2023-09-22 5:02 ` Heng Qi
2023-09-22 7:32 ` Jason Wang
2023-09-22 7:58 ` Heng Qi [this message]
2023-09-25 2:29 ` Jason Wang
2023-09-25 2:47 ` Heng Qi
2023-09-22 9:50 ` Xuan Zhuo
2023-09-25 2:29 ` Jason Wang
2023-09-25 2:45 ` Heng Qi
2023-09-19 7:49 ` [PATCH net 6/6] virtio-net: a tiny comment update Heng Qi
2023-09-22 4:30 ` 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=2ffd0e15-107e-4c46-8d98-caf47ff6a0c6@linux.alibaba.com \
--to=hengqi@linux.alibaba.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gavinl@nvidia.com \
--cc=hawk@kernel.org \
--cc=jasowang@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=mst@redhat.com \
--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