From: "Gray, Mark D" <mark.d.gray@intel.com>
To: GongJinrong <jinronggong@hotmail.com>,
'Thomas Monjalon' <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Can anyone help me to run the l2fwd-ivshmem example?
Date: Wed, 18 Jun 2014 08:52:52 +0000 [thread overview]
Message-ID: <738D45BC1F695740A983F43CFE1B7EA91B215B37@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <COL402-EAS3350292795F02565752A9D5B7100@phx.gbl>
>
> 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.
next prev parent reply other threads:[~2014-06-18 8:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 7:56 GongJinrong
2014-06-18 8:19 ` Thomas Monjalon
2014-06-18 8:42 ` GongJinrong
2014-06-18 8:52 ` Gray, Mark D [this message]
2014-06-18 9:18 ` GongJinrong
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=738D45BC1F695740A983F43CFE1B7EA91B215B37@IRSMSX102.ger.corp.intel.com \
--to=mark.d.gray@intel.com \
--cc=dev@dpdk.org \
--cc=jinronggong@hotmail.com \
--cc=thomas.monjalon@6wind.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).