From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: kvm@vger.kernel.org, netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org, wexu@redhat.com,
stefanha@redhat.com
Subject: Re: [PATCH V4 net-next 1/3] vhost: better detection of available buffers
Date: Tue, 10 Jan 2017 01:10:41 +0200 [thread overview]
Message-ID: <20170110010957-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <e09ccb6a-87b8-d2b1-f64d-79ea7ea89954@redhat.com>
On Mon, Jan 09, 2017 at 10:59:16AM +0800, Jason Wang wrote:
>
>
> On 2017年01月07日 03:55, Michael S. Tsirkin wrote:
> > On Fri, Jan 06, 2017 at 10:13:15AM +0800, Jason Wang wrote:
> > > This patch tries to do several tweaks on vhost_vq_avail_empty() for a
> > > better performance:
> > >
> > > - check cached avail index first which could avoid userspace memory access.
> > > - using unlikely() for the failure of userspace access
> > > - check vq->last_avail_idx instead of cached avail index as the last
> > > step.
> > >
> > > This patch is need for batching supports which needs to peek whether
> > > or not there's still available buffers in the ring.
> > >
> > > Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
> > > Signed-off-by: Jason Wang <jasowang@redhat.com>
> > > ---
> > > drivers/vhost/vhost.c | 8 ++++++--
> > > 1 file changed, 6 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c
> > > index d643260..9f11838 100644
> > > --- a/drivers/vhost/vhost.c
> > > +++ b/drivers/vhost/vhost.c
> > > @@ -2241,11 +2241,15 @@ bool vhost_vq_avail_empty(struct vhost_dev *dev, struct vhost_virtqueue *vq)
> > > __virtio16 avail_idx;
> > > int r;
> > > + if (vq->avail_idx != vq->last_avail_idx)
> > > + return false;
> > > +
> > > r = vhost_get_user(vq, avail_idx, &vq->avail->idx);
> > > - if (r)
> > > + if (unlikely(r))
> > > return false;
> > > + vq->avail_idx = vhost16_to_cpu(vq, avail_idx);
> > > - return vhost16_to_cpu(vq, avail_idx) == vq->avail_idx;
> > > + return vq->avail_idx == vq->last_avail_idx;
> > > }
> > > EXPORT_SYMBOL_GPL(vhost_vq_avail_empty);
> > So again, this did not address the issue I pointed out in v1:
> > if we have 1 buffer in RX queue and
> > that is not enough to store the whole packet,
> > vhost_vq_avail_empty returns false, then we re-read
> > the descriptors again and again.
> >
> > You have saved a single index access but not the more expensive
> > descriptor access.
>
> Looks not, if I understand the code correctly, in this case, get_rx_bufs()
> will return zero, and we will try to enable rx kick and exit the loop.
>
> Thanks
I mean this:
while (vhost_can_busy_poll(vq->dev, endtime) &&
vhost_vq_avail_empty(vq->dev, vq))
cpu_relax();
preempt_enable();
r = vhost_get_vq_desc(vq, vq->iov, ARRAY_SIZE(vq->iov),
out_num, in_num, NULL, NULL);
vhost_vq_avail_empty returns false so we break out of the loop
and call vhost_get_vq_desc.
--
MST
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2017-01-09 23:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 2:13 [PATCH V4 net-next 0/3] vhost_net tx batching Jason Wang
2017-01-06 2:13 ` [PATCH V4 net-next 1/3] vhost: better detection of available buffers Jason Wang
2017-01-06 19:55 ` Michael S. Tsirkin
2017-01-09 2:59 ` Jason Wang
2017-01-09 23:10 ` Michael S. Tsirkin [this message]
2017-01-10 2:22 ` Jason Wang
2017-01-10 2:57 ` Michael S. Tsirkin
2017-01-06 2:13 ` [PATCH V4 net-next 2/3] vhost_net: tx batching Jason Wang
2017-01-06 2:13 ` [PATCH V4 net-next 3/3] tun: rx batching Jason Wang
2017-01-06 19:47 ` Michael S. Tsirkin
2017-01-09 2:39 ` Jason Wang
2017-01-09 23:12 ` Michael S. Tsirkin
2017-01-10 2:24 ` 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=20170110010957-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=wexu@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).