From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: dev@dpdk.org, chenbo.xia@intel.com, yux.jiang@intel.com,
thomas@monjalon.net, david.marchand@redhat.com
Subject: Re: [PATCH] vhost: fix missing copy length in batched copies
Date: Tue, 12 Jul 2022 12:09:46 +0200 [thread overview]
Message-ID: <a3d23a06-dc0d-497b-6019-91fdf0bd113c@redhat.com> (raw)
In-Reply-To: <20220712100447.104162-1-maxime.coquelin@redhat.com>
On 7/12/22 12:04, Maxime Coquelin wrote:
> This patch fixes missing the assignement of the copy length
s/assignement/assignment/
If this is the only change requested, could it be fixed while applying,
or should I send a v2?
Thanks,
Maxime
> when doing batched copies in the sync dequeue path.
>
> Fixes: cd79d1b030bd ("vhost: fix unnecessary dirty page logging")
>
> Suggested-by: Chenbo Xia <chenbo.xia@intel.com>
> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> ---
> lib/vhost/virtio_net.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/vhost/virtio_net.c b/lib/vhost/virtio_net.c
> index 12b7fbe7f9..35fa4670fd 100644
> --- a/lib/vhost/virtio_net.c
> +++ b/lib/vhost/virtio_net.c
> @@ -1127,13 +1127,13 @@ sync_fill_seg(struct virtio_net *dev, struct vhost_virtqueue *vq,
> batch_copy[vq->batch_copy_nb_elems].src =
> rte_pktmbuf_mtod_offset(m, void *, mbuf_offset);
> batch_copy[vq->batch_copy_nb_elems].log_addr = buf_iova;
> - batch_copy[vq->batch_copy_nb_elems].len = cpy_len;
> } else {
> batch_copy[vq->batch_copy_nb_elems].dst =
> rte_pktmbuf_mtod_offset(m, void *, mbuf_offset);
> batch_copy[vq->batch_copy_nb_elems].src =
> (void *)((uintptr_t)(buf_addr));
> }
> + batch_copy[vq->batch_copy_nb_elems].len = cpy_len;
> vq->batch_copy_nb_elems++;
> }
> }
next prev parent reply other threads:[~2022-07-12 10:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 10:04 Maxime Coquelin
2022-07-12 10:09 ` Maxime Coquelin [this message]
2022-07-12 10:15 ` Xia, Chenbo
2022-07-13 8:33 ` Ling, WeiX
2022-07-14 13:32 ` Thomas Monjalon
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=a3d23a06-dc0d-497b-6019-91fdf0bd113c@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=chenbo.xia@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yux.jiang@intel.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).