From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "O'Driscoll, Tim" <tim.odriscoll@intel.com>,
dev@dpdk.org, Maxime Coquelin <maxime.coquelin@redhat.com>,
"Harris, James R" <james.r.harris@intel.com>,
"Liu, Changpeng" <changpeng.liu@intel.com>
Subject: Re: [dpdk-dev] 17.02 Roadmap
Date: Tue, 11 Oct 2016 13:32:18 +0800 [thread overview]
Message-ID: <20161011053218.GL1597@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <1998191.9HGrB6oKr3@xps13>
On Mon, Oct 10, 2016 at 10:42:58PM +0200, Thomas Monjalon wrote:
> > Support New Device Types in Vhost-User: Support will be added to vhost-user for new device types including vhost-scsi and vhost-blk.
>
> Great!
> Is it only related to networking or should we expect some storage-related
> code or drivers to come up?
It's not only netowrking related. It just introduces few more APIs to
export those buf infos (virt addr, phys addr, len, etc) to applications,
so that they can handle/parse the data in the way they want. For example,
for SPDK (https://01.org/spdk), they can use those APIs to fetch guest
data and parse it following virtio-SCSI spec.
The dequeue path (guest Tx) might look like something below:
rte_vhost_dequeue_vring_desc_burst(vid, queue_id, iov, count)
{
for (i = 0; i < count; i++) {
desc_idx = get_next_desc();
iov[i]->addr = desc_virt_addr(desc[desc_idx]->addr);
iov[i]->phys_addr = desc_phys_addr(desc[desc_idx]->addr);
iov[i]->len = desc[desc_idx]->len;
iov[i]->desc = desc_idx;
}
return i;
}
rte_vhost_update_used_ring(vid, queue_id, descs, count)
{
for (i = 0; i < count; i++) {
used_idx = get_next_used_idx();
vq->used->ring[used_idx] = descs[i];
}
vq->used->idx += i;
}
And we introduce similar APIs to the enqueue path.
--yliu
next prev parent reply other threads:[~2016-10-11 5:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 16:13 O'Driscoll, Tim
2016-10-10 20:42 ` Thomas Monjalon
2016-10-11 5:32 ` Yuanhan Liu [this message]
2016-10-11 9:09 ` O'Driscoll, Tim
2016-10-11 10:25 ` Pattan, Reshma
2016-10-11 22:36 ` De Lara Guarch, Pablo
2016-10-13 3:15 ` Tan, Jianfeng
2016-10-13 14:18 ` Hunt, David
2016-10-13 14:39 ` Thomas Monjalon
2016-10-14 17:29 ` Stephen Hemminger
2016-10-14 20:18 ` Thomas Monjalon
2016-10-16 20:21 ` O'Driscoll, Tim
-- strict thread matches above, loose matches on Subject: below --
2016-08-31 10:31 O'Driscoll, Tim
2016-08-31 12:07 ` 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=20161011053218.GL1597@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=changpeng.liu@intel.com \
--cc=dev@dpdk.org \
--cc=james.r.harris@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=thomas.monjalon@6wind.com \
--cc=tim.odriscoll@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).