DPDK patches and discussions
 help / color / mirror / Atom feed
From: GongJinrong <jinronggong@hotmail.com>
To: "'Hiroshi Shimamoto'" <h-shimamoto@ct.jp.nec.com>,
	"'Thomas Monjalon'" <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Testing memnic for VM to VM transfer
Date: Wed, 18 Jun 2014 20:25:55 +0800	[thread overview]
Message-ID: <COL402-EAS380AA4137DDC7EF0A48D55BB7100@phx.gbl> (raw)
In-Reply-To: <7F861DC0615E0C47A872E6F3C5FCDDBD0111B348@BPXM14GP.gisp.nec.co.jp>

Thanks guys, I will try.

-----Original Message-----
From: Hiroshi Shimamoto [mailto:h-shimamoto@ct.jp.nec.com] 
Sent: Wednesday, June 18, 2014 8:06 PM
To: Thomas Monjalon; GongJinrong
Cc: dev@dpdk.org; 'John Joyce (joycej)'; Olivier MATZ
Subject: RE: [dpdk-dev] Testing memnic for VM to VM transfer

Hi,

> Subject: Re: [dpdk-dev] Testing memnic for VM to VM transfer
> 
> 2014-06-18 11:42, Hiroshi Shimamoto:
> > 2014-06-18 19:26, GongJinrong:
> > > Do you have any idea that how to write a host application to put 
> > > the data to guest memnic PMD?
> >
> > Yes, basically I made the MEMNIC interface work with DPDK vSwitch.
> >
> > By the way, you can mmap() the shm which specified as the ivshmem 
> > and put the proper data to send a packet to guest PMD.
> > I don't have time to make proper code, but can advise you; please 
> > see common/memnic.h and the memory layout.
> > 1) Set magic and version in header on host.
> > 2) Initialize PMD on guest.
> > 3) Check the reset is 1 and set valid to 1, reset to 0 on host.
> > 4) Use uplink area the default block size 4K.
> >    Set len and fill ether frame data, then set the status to 2 on host.
> >    Guest PMD may receive the packet.
> >    Proceed to the next packet block.
> 
> Such application should be integrated in memnic repository.
> I know Olivier wrote one which could be sent on next week.

yeah, I just begin to feel to need such a software in the repository.

thanks,
Hiroshi

> 
> --
> Thomas

  reply	other threads:[~2014-06-18 12:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-18 11:42 Hiroshi Shimamoto
2014-06-18 11:49 ` Thomas Monjalon
2014-06-18 12:06   ` Hiroshi Shimamoto
2014-06-18 12:25     ` GongJinrong [this message]
2014-07-02 15:59     ` Thomas Monjalon
2014-07-03  6:34       ` GongJinrong
2014-07-03 11:03         ` GongJinrong
2014-07-03 12:05           ` Thomas Monjalon
2014-07-07  9:58             ` xie huawei
2014-07-07 10:05               ` Thomas Monjalon
  -- strict thread matches above, loose matches on Subject: below --
2014-06-13 15:29 John Joyce (joycej)
2014-06-18  4:02 ` Hiroshi Shimamoto
2014-06-18 10: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=COL402-EAS380AA4137DDC7EF0A48D55BB7100@phx.gbl \
    --to=jinronggong@hotmail.com \
    --cc=dev@dpdk.org \
    --cc=h-shimamoto@ct.jp.nec.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).