[dpdk-dev] Can anyone help me to run the l2fwd-ivshmem example?

GongJinrong jinronggong at hotmail.com
Wed Jun 18 11:18:30 CEST 2014


Thanks, Mark, the comment is really help.

-----Original Message-----
From: Gray, Mark D [mailto:mark.d.gray at intel.com] 
Sent: Wednesday, June 18, 2014 4:53 PM
To: GongJinrong; 'Thomas Monjalon'
Cc: dev at dpdk.org
Subject: RE: [dpdk-dev] Can anyone help me to run the l2fwd-ivshmem example?

> 
> Hi,
> 
> 2014-06-18 15:56, GongJinrong:
> >    I want find a zero copy framework from host to vm without any 
> > physical NIC device,
> 
> I think memnic is what you want:
> 	http://dpdk.org/doc/memnic-pmd
> 
> > it seems l2fwd-ivshmem can be used, but I have problems to run this
> > example:
> >    1. there is no document about this example, even a simple readme :-(
> >    2. does this example need ovdk?
> 
> No
> 
> >    3. can I use standard qemu to run this example? Does the standard 
> > qemu support ivshmem?
> 
> You should be able to use standard Qemu.

Standard QEMU will work for Memnic but not when using DPDK ivshmem. It uses
the standard QEMU ivshem and doesn't use DPDK in the way you would like it
to

You should look at  the DPDK vSwitch code to see how DPDK ivshmem is used. 
Basically, in the host you need to identify what objects that you want to
share with the virtual machine

e.g. rings, memzones

>From this, you can generate a command line to pass to QEMU (with a modified
ivshmem.c file
- we haven't tried to upstream this yet)

Then when you start a DPDK application in the guest, each of the objects
that you shared from the host are also available in the guest.

I presume the l2fwd-ivshmem does the same

> 
> --
> Thomas
--------------------------------------------------------------
Intel Shannon Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263 Business address: Dromore House, East Park,
Shannon, Co. Clare

This e-mail and any attachments may contain confidential material for the
sole use of the intended recipient(s). Any review or distribution by others
is strictly prohibited. If you are not the intended recipient, please
contact the sender and delete all copies.




More information about the dev mailing list