DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev] OVDK userspace vhost : Issue with VIRTIO_RING_F_INDIRECT_DESC capability
@ 2015-07-01 12:02 sai kiran
  2015-07-02  8:20 ` Gray, Mark D
  0 siblings, 1 reply; 2+ messages in thread
From: sai kiran @ 2015-07-01 12:02 UTC (permalink / raw)
  To: dev

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*

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [dpdk-dev] OVDK userspace vhost : Issue with VIRTIO_RING_F_INDIRECT_DESC capability
  2015-07-01 12:02 [dpdk-dev] OVDK userspace vhost : Issue with VIRTIO_RING_F_INDIRECT_DESC capability sai kiran
@ 2015-07-02  8:20 ` Gray, Mark D
  0 siblings, 0 replies; 2+ messages in thread
From: Gray, Mark D @ 2015-07-02  8:20 UTC (permalink / raw)
  To: sai kiran, dev, dpdk-ovs

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*

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-07-02  8:20 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-07-01 12:02 [dpdk-dev] OVDK userspace vhost : Issue with VIRTIO_RING_F_INDIRECT_DESC capability sai kiran
2015-07-02  8:20 ` Gray, Mark D

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).