From: "Fu, Patrick" <patrick.fu@intel.com>
To: "Xia, Chenbo" <chenbo.xia@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>
Subject: Re: [dpdk-dev] [PATCH v3] vhost: fix async copy fail on multi-page buffers
Date: Tue, 28 Jul 2020 03:09:57 +0000 [thread overview]
Message-ID: <DM5PR1101MB21697DAAC72F4C667DD47FA184730@DM5PR1101MB2169.namprd11.prod.outlook.com> (raw)
In-Reply-To: <MN2PR11MB406339F299709F95B8EA231B9C720@MN2PR11MB4063.namprd11.prod.outlook.com>
Hi,
> -----Original Message-----
> From: Xia, Chenbo <chenbo.xia@intel.com>
> Sent: Monday, July 27, 2020 9:14 PM
> To: Fu, Patrick <patrick.fu@intel.com>; dev@dpdk.org;
> maxime.coquelin@redhat.com
> Subject: RE: [PATCH v3] vhost: fix async copy fail on multi-page buffers
>
> Hi Patrick,
>
> > -----Original Message-----
> > From: Fu, Patrick <patrick.fu@intel.com>
> > Sent: Monday, July 27, 2020 2:33 PM
> > To: dev@dpdk.org; maxime.coquelin@redhat.com; Xia, Chenbo
> > <chenbo.xia@intel.com>
> > Cc: Fu, Patrick <patrick.fu@intel.com>
> > Subject: [PATCH v3] vhost: fix async copy fail on multi-page buffers
> >
> > lib/librte_vhost/vhost.h | 50 +++++++++++++++++++++++++++++++++++
> > lib/librte_vhost/virtio_net.c | 40 +++++++++++++++++-----------
> > 2 files changed, 75 insertions(+), 15 deletions(-)
> >
> > + } else {
> > + for (i = 0; i < dev->nr_guest_pages; i++) {
> > + page = &dev->guest_pages[i];
> > +
> > + if (gpa >= page->guest_phys_addr) {
> > + if (gpa + gpa_size <
>
> Should the '<' be '<=' here?
>
Yes, it should be. Will update in v4 patch
> > static __rte_always_inline uint64_t
> > hva_to_gpa(struct virtio_net *dev, uint64_t vva, uint64_t len) {
> > diff --git a/lib/librte_vhost/virtio_net.c
> > b/lib/librte_vhost/virtio_net.c index
> > 95a0bc19f..124a33a10 100644
> > --- a/lib/librte_vhost/virtio_net.c
> > +++ b/lib/librte_vhost/virtio_net.c
> > @@ -980,6 +980,7 @@ async_mbuf_to_desc(struct virtio_net *dev, struct
> > vhost_virtqueue *vq,
> > struct batch_copy_elem *batch_copy = vq->batch_copy_elems;
> > struct virtio_net_hdr_mrg_rxbuf tmp_hdr, *hdr = NULL;
> > int error = 0;
> > + uint64_t mapped_len;
> >
> > uint32_t tlen = 0;
> > int tvec_idx = 0;
> > @@ -1072,24 +1073,31 @@ async_mbuf_to_desc(struct virtio_net *dev,
> > struct vhost_virtqueue *vq,
> >
> > cpy_len = RTE_MIN(buf_avail, mbuf_avail);
> >
> > - if (unlikely(cpy_len >= cpy_threshold)) {
> > - hpa = (void *)(uintptr_t)gpa_to_hpa(dev,
> > - buf_iova + buf_offset, cpy_len);
> > + while (unlikely(cpy_len && cpy_len >= cpy_threshold)) {
> > + hpa = (void *)(uintptr_t)gpa_to_first_hpa(dev,
> > + buf_iova + buf_offset,
> > + cpy_len, &mapped_len);
> >
> > - if (unlikely(!hpa)) {
> > - error = -1;
> > - goto out;
> > - }
> > + if (unlikely(!hpa || mapped_len < cpy_threshold))
> > + break;
> >
> > async_fill_vec(src_iovec + tvec_idx,
> > (void *)(uintptr_t)rte_pktmbuf_iova_offset(m,
> > - mbuf_offset), cpy_len);
> > + mbuf_offset), (size_t)mapped_len);
> >
> > - async_fill_vec(dst_iovec + tvec_idx, hpa, cpy_len);
> > + async_fill_vec(dst_iovec + tvec_idx,
> > + hpa, (size_t)mapped_len);
> >
> > - tlen += cpy_len;
> > + tlen += (uint32_t)mapped_len;
> > + cpy_len -= (uint32_t)mapped_len;
> > + mbuf_avail -= (uint32_t)mapped_len;
> > + mbuf_offset += (uint32_t)mapped_len;
> > + buf_avail -= (uint32_t)mapped_len;
> > + buf_offset += (uint32_t)mapped_len;
>
> Will it be ok we just transform the uint64_t to uint32_t here?
> What if mapped_len > MAX uint32_t ?
>
"mapped_len" could not exceed "cpy_len" (according to the gpa_to_first_hpa() logic). As cpy_len is uint32, mapped_len is safe to down casting.
Thanks,
Patrick
next prev parent reply other threads:[~2020-07-28 3:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 2:52 [dpdk-dev] [PATCH v1] vhost: support cross page buf in async data path patrick.fu
2020-07-20 16:39 ` Maxime Coquelin
2020-07-21 2:57 ` Fu, Patrick
2020-07-21 8:35 ` Maxime Coquelin
2020-07-21 9:01 ` Fu, Patrick
2020-07-24 13:49 ` [dpdk-dev] [PATCH v2] vhost: fix async copy fail on multi-page buffers patrick.fu
2020-07-27 6:33 ` [dpdk-dev] [PATCH v3] " patrick.fu
2020-07-27 13:14 ` Xia, Chenbo
2020-07-28 3:09 ` Fu, Patrick [this message]
2020-07-28 3:28 ` [dpdk-dev] [PATCH v4] " patrick.fu
2020-07-28 13:55 ` Maxime Coquelin
2020-07-29 1:40 ` Fu, Patrick
2020-07-29 2:05 ` Fu, Patrick
2020-07-29 2:04 ` [dpdk-dev] [PATCH v5] " Patrick Fu
2020-07-29 14:24 ` Maxime Coquelin
2020-07-29 14:55 ` Maxime Coquelin
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=DM5PR1101MB21697DAAC72F4C667DD47FA184730@DM5PR1101MB2169.namprd11.prod.outlook.com \
--to=patrick.fu@intel.com \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.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).