From: Stefan Hajnoczi <stefanha@gmail.com>
To: Jason Wang <jasowang@redhat.com>
Cc: mst@redhat.com, virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org
Subject: Re: [PATCH net-next RFC 1/5] vhost: split out ring head fetching logic
Date: Fri, 22 Sep 2017 09:31:58 +0100 [thread overview]
Message-ID: <20170922083157.GA9243@stefanha-x1.localdomain> (raw)
In-Reply-To: <1506067355-5771-2-git-send-email-jasowang@redhat.com>
On Fri, Sep 22, 2017 at 04:02:31PM +0800, Jason Wang wrote:
> +/* This looks in the virtqueue and for the first available buffer, and converts
> + * it to an iovec for convenient access. Since descriptors consist of some
> + * number of output then some number of input descriptors, it's actually two
> + * iovecs, but we pack them into one and note how many of each there were.
> + *
> + * This function returns the descriptor number found, or vq->num (which is
> + * never a valid descriptor number) if none was found. A negative code is
> + * returned on error. */
> +int __vhost_get_vq_desc(struct vhost_virtqueue *vq,
> + struct iovec iov[], unsigned int iov_size,
> + unsigned int *out_num, unsigned int *in_num,
> + struct vhost_log *log, unsigned int *log_num,
> + __virtio16 head)
[...]
> +int vhost_get_vq_desc(struct vhost_virtqueue *vq,
> + struct iovec iov[], unsigned int iov_size,
> + unsigned int *out_num, unsigned int *in_num,
> + struct vhost_log *log, unsigned int *log_num)
Please document vhost_get_vq_desc().
Please also explain the difference between __vhost_get_vq_desc() and
vhost_get_vq_desc() in the documentation.
next prev parent reply other threads:[~2017-09-22 8:32 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 8:02 [PATCH net-next RFC 0/5] batched tx processing in vhost_net Jason Wang
2017-09-22 8:02 ` [PATCH net-next RFC 1/5] vhost: split out ring head fetching logic Jason Wang
2017-09-22 8:31 ` Stefan Hajnoczi [this message]
2017-09-25 2:03 ` Jason Wang
2017-09-22 8:02 ` [PATCH net-next RFC 2/5] vhost: introduce helper to prefetch desc index Jason Wang
2017-09-22 9:02 ` Stefan Hajnoczi
2017-09-25 2:04 ` Jason Wang
2017-09-26 19:19 ` Michael S. Tsirkin
2017-09-27 0:35 ` Jason Wang
2017-09-27 22:57 ` Michael S. Tsirkin
2017-09-28 7:18 ` Jason Wang
2017-09-28 0:47 ` Willem de Bruijn
2017-09-28 7:44 ` Jason Wang
2017-09-22 8:02 ` [PATCH net-next RFC 3/5] vhost: introduce vhost_add_used_idx() Jason Wang
2017-09-22 9:07 ` Stefan Hajnoczi
2017-09-26 19:13 ` Michael S. Tsirkin
2017-09-27 0:38 ` Jason Wang
2017-09-27 22:58 ` Michael S. Tsirkin
2017-09-28 0:59 ` Willem de Bruijn
2017-09-28 7:19 ` Jason Wang
2017-09-22 8:02 ` [PATCH net-next RFC 4/5] vhost_net: rename VHOST_RX_BATCH to VHOST_NET_BATCH Jason Wang
2017-09-22 8:02 ` [PATCH net-next RFC 5/5] vhost_net: basic tx virtqueue batched processing Jason Wang
2017-09-26 19:25 ` Michael S. Tsirkin
2017-09-27 2:04 ` Jason Wang
2017-09-27 22:19 ` Michael S. Tsirkin
2017-09-28 7:02 ` Jason Wang
2017-09-28 7:52 ` Jason Wang
2017-09-28 0:55 ` Willem de Bruijn
2017-09-28 7:50 ` Jason Wang
2017-09-26 13:45 ` [PATCH net-next RFC 0/5] batched tx processing in vhost_net Michael S. Tsirkin
2017-09-27 0:27 ` Jason Wang
2017-09-27 22:28 ` Michael S. Tsirkin
2017-09-28 7:16 ` Jason Wang
2017-09-26 19:26 ` Michael S. Tsirkin
2017-09-27 2:06 ` 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=20170922083157.GA9243@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
/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
all inboxes | Powered by JetHome®