From: Simon Horman <horms@kernel.org>
To: Heng Qi <hengqi@linux.alibaba.com>
Cc: netdev@vger.kernel.org, virtualization@lists.linux.dev,
Jason Wang <jasowang@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Paolo Abeni <pabeni@redhat.com>, Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
"David S. Miller" <davem@davemloft.net>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Subject: Re: [PATCH net-next 2/3] virtio-net: batch dim request
Date: Tue, 16 Jan 2024 19:49:12 +0000 [thread overview]
Message-ID: <20240116194912.GE588419@kernel.org> (raw)
In-Reply-To: <1705410693-118895-3-git-send-email-hengqi@linux.alibaba.com>
On Tue, Jan 16, 2024 at 09:11:32PM +0800, Heng Qi wrote:
> Currently, when each time the driver attempts to update the coalescing
> parameters for a vq, it needs to kick the device.
> The following path is observed:
> 1. Driver kicks the device;
> 2. After the device receives the kick, CPU scheduling occurs and DMA
> multiple buffers multiple times;
> 3. The device completes processing and replies with a response.
>
> When large-queue devices issue multiple requests and kick the device
> frequently, this often interrupt the work of the device-side CPU.
> In addition, each vq request is processed separately, causing more
> delays for the CPU to wait for the DMA request to complete.
>
> These interruptions and overhead will strain the CPU responsible for
> controlling the path of the DPU, especially in multi-device and
> large-queue scenarios.
>
> To solve the above problems, we internally tried batch request,
> which merges requests from multiple queues and sends them at once.
> We conservatively tested 8 queue commands and sent them together.
> The DPU processing efficiency can be improved by 8 times, which
> greatly eases the DPU's support for multi-device and multi-queue DIM.
>
> Suggested-by: Xiaoming Zhao <zxm377917@alibaba-inc.com>
> Signed-off-by: Heng Qi <hengqi@linux.alibaba.com>
...
> @@ -3546,16 +3552,32 @@ static void virtnet_rx_dim_work(struct work_struct *work)
> update_moder = net_dim_get_rx_moderation(dim->mode, dim->profile_ix);
> if (update_moder.usec != rq->intr_coal.max_usecs ||
> update_moder.pkts != rq->intr_coal.max_packets) {
> - err = virtnet_send_rx_ctrl_coal_vq_cmd(vi, qnum,
> - update_moder.usec,
> - update_moder.pkts);
> - if (err)
> - pr_debug("%s: Failed to send dim parameters on rxq%d\n",
> - dev->name, qnum);
> - dim->state = DIM_START_MEASURE;
> + coal->coal_vqs[j].vqn = cpu_to_le16(rxq2vq(i));
> + coal->coal_vqs[j].coal.max_usecs = cpu_to_le32(update_moder.usec);
> + coal->coal_vqs[j].coal.max_packets = cpu_to_le32(update_moder.pkts);
> + rq->intr_coal.max_usecs = update_moder.usec;
> + rq->intr_coal.max_packets = update_moder.pkts;
> + j++;
> }
> }
>
> + if (!j)
> + goto ret;
> +
> + coal->num_entries = cpu_to_le32(j);
> + sg_init_one(&sgs, coal, sizeof(struct virtnet_batch_coal) +
> + j * sizeof(struct virtio_net_ctrl_coal_vq));
> + if (!virtnet_send_command(vi, VIRTIO_NET_CTRL_NOTF_COAL,
> + VIRTIO_NET_CTRL_NOTF_COAL_VQS_SET,
> + &sgs))
> + dev_warn(&vi->vdev->dev, "Failed to add dim command\n.");
> +
> + for (i = 0; i < j; i++) {
> + rq = &vi->rq[(coal->coal_vqs[i].vqn) / 2];
Hi Heng Qi,
The type of .vqn is __le16, but here it is used as an
integer in host byte order. Perhaps this should be (completely untested!):
rq = &vi->rq[le16_to_cpu(coal->coal_vqs[i].vqn) / 2];
> + rq->dim.state = DIM_START_MEASURE;
> + }
> +
> +ret:
> rtnl_unlock();
> }
>
next prev parent reply other threads:[~2024-01-16 19:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 13:11 [PATCH net-next 0/3] virtio-net: a fix and some updates for virtio dim Heng Qi
2024-01-16 13:11 ` [PATCH net-next 1/3] virtio-net: fix possible dim status unrecoverable Heng Qi
2024-01-16 13:15 ` Michael S. Tsirkin
2024-01-17 3:34 ` Heng Qi
2024-01-16 13:11 ` [PATCH net-next 2/3] virtio-net: batch dim request Heng Qi
2024-01-16 19:49 ` Simon Horman [this message]
2024-01-17 3:38 ` Heng Qi
2024-01-16 13:11 ` [PATCH net-next 3/3] virtio-net: reduce the CPU consumption of dim worker Heng Qi
2024-01-16 19:56 ` Simon Horman
2024-01-17 3:41 ` Heng Qi
2024-01-19 10:31 ` kernel test robot
2024-01-19 13:43 ` kernel test robot
2024-01-22 7:19 ` Xuan Zhuo
2024-01-22 7:42 ` Xuan Zhuo
2024-01-19 12:28 ` [PATCH net-next 0/3] virtio-net: a fix and some updates for virtio dim Michael S. Tsirkin
2024-01-19 14:20 ` Heng Qi
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=20240116194912.GE588419@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hengqi@linux.alibaba.com \
--cc=jasowang@redhat.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).