From: "Gray, Mark D" <mark.d.gray@intel.com>
To: sai kiran <kiransaiv@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>,
"dpdk-ovs@lists.01.org" <dpdk-ovs@lists.01.org>
Subject: Re: [dpdk-dev] OVDK userspace vhost : Issue with VIRTIO_RING_F_INDIRECT_DESC capability
Date: Thu, 2 Jul 2015 08:20:34 +0000 [thread overview]
Message-ID: <738D45BC1F695740A983F43CFE1B7EA92E2A8F27@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <CAAcJOpWXA7e2NJvG6AnwzxBstWKdbpZZj-5X=vcTHV2qc4QtoQ@mail.gmail.com>
Cross posting to OVDK list.
On a side point, Have you looked at the DPDK enabled build in upstream OVS?
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of sai kiran
> Sent: Wednesday, July 1, 2015 1:02 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] OVDK userspace vhost : Issue with
> VIRTIO_RING_F_INDIRECT_DESC capability
>
> Hi,
>
> I am using OVDK userspace-vhost interfaces for VM-to-external
> communication and facing an issue with them.
>
> I am using the topology mentioned in
> https://github.com/01org/dpdk-
> ovs/blob/development/docs/04_Sample_Configurations/02_Userspace-
> vHost.md
> But the Guest is a Freebsd VM and our own custom userspace virtio drivers.
> Guest does not have DPDK.
>
>
> 1. I could start OVDK application and vswitchd, and provision a FreeBSD
> Guest VM with two userspace-vhost interfaces.
> 2. These two userspace-vhost interfaces do not have
> VIRTIO_RING_F_INDIRECT_DESC
> capability negotiated from backend OVDK-Qemu
> 3. Inside the freebsd VM, i have my own userspace drivers running, which
> make use of indirect descriptors of virtio.
> 4. *Question 1* : By default, without INDIRECT descriptor capability, my
> drivers fail to run. Is there any way to increase ring size of
> virtio? This can help us avoid using indirect descriptors because of
> more space in the ring
> 5. *Question 2*: When I try to set the capability from backend QEMU,
> guest drivers do not see any packets reaching the guest. Is there
> any way to resolve this ??
>
> Any help/suggestion would be of great help.
>
> *Thanks & Regards,*
> *Saikiran V*
prev parent reply other threads:[~2015-07-02 8:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 12:02 sai kiran
2015-07-02 8:20 ` Gray, Mark D [this message]
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=738D45BC1F695740A983F43CFE1B7EA92E2A8F27@IRSMSX108.ger.corp.intel.com \
--to=mark.d.gray@intel.com \
--cc=dev@dpdk.org \
--cc=dpdk-ovs@lists.01.org \
--cc=kiransaiv@gmail.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).