All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: GongJinrong <jinronggong-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: About ivshmem
Date: Wed, 11 Jun 2014 11:19:57 +0200	[thread overview]
Message-ID: <3065658.RY5fKXJfpQ@xps13> (raw)
In-Reply-To: <COL402-EAS378C4BD0B3BA653449BA9D7B72B0-MsuGFMq8XAE@public.gmane.org>

Hi,

2014-06-11 16:53, GongJinrong:
>     I found that the ivshmem are supported in DPDK 1.6 but has no any
> document about it, how do I use ivshmem? I remember that we must use a
> patched qemu binary for enabling ivshmem support in OVDK, does DPDK 1.6 also
> need do this? Also, where can I find some ivshmem docs?

If you're looking for information about OVDK, you should ask on the
appropriate mailing list.

If you are looking for a PMD using ivshmem, you should look at memnic:
	http://dpdk.org/doc/memnic-pmd

-- 
Thomas

  parent reply	other threads:[~2014-06-11  9:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11  8:53 About ivshmem GongJinrong
     [not found] ` <COL402-EAS378C4BD0B3BA653449BA9D7B72B0-MsuGFMq8XAE@public.gmane.org>
2014-06-11  9:19   ` Thomas Monjalon [this message]
2014-06-11  9:24     ` Gray, Mark D
     [not found]       ` <738D45BC1F695740A983F43CFE1B7EA91B212567-kPTMFJFq+rFP9JyJpTNKArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-06-11 10:13         ` GongJinrong
     [not found]           ` <COL402-EAS52B761AB128EE28C402AF2B72B0-MsuGFMq8XAE@public.gmane.org>
2014-06-11 10:30             ` Gray, Mark D
     [not found]               ` <738D45BC1F695740A983F43CFE1B7EA91B212619-kPTMFJFq+rFP9JyJpTNKArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-06-11 10:36                 ` GongJinrong
2014-06-11 11:29                 ` 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=3065658.RY5fKXJfpQ@xps13 \
    --to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=jinronggong-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.