From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: Hiroshi Shimamoto <h-shimamoto-ehU+Cx/zZe18UrSeD/g0lQ@public.gmane.org>
Cc: "dev-VfR2kkLFssw@public.gmane.org" <dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: Testing memnic for VM to VM transfer
Date: Wed, 02 Jul 2014 08:59:06 -0700 (PDT) [thread overview]
Message-ID: <3856470.KKoi0bR8VV@xps13> (raw)
In-Reply-To: <7F861DC0615E0C47A872E6F3C5FCDDBD0111B348-ZmjkEB1lVlLt6d3pZDjeaEtBU8KWyXPq@public.gmane.org>
2014-06-18 12:06, Hiroshi Shimamoto:
> 2014-06-18 13:49, Thomas Monjalon:
> > 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.
I've pushed the test application (host-sim) that Olivier wrote.
Feel free to improve it.
I think that we could also use the PMD driver in host side with some
modifications.
--
Thomas
next prev parent reply other threads:[~2014-07-02 15:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 11:42 Testing memnic for VM to VM transfer Hiroshi Shimamoto
[not found] ` <7F861DC0615E0C47A872E6F3C5FCDDBD0111B25E-ZmjkEB1lVlLt6d3pZDjeaEtBU8KWyXPq@public.gmane.org>
2014-06-18 11:49 ` Thomas Monjalon
2014-06-18 12:06 ` Hiroshi Shimamoto
[not found] ` <7F861DC0615E0C47A872E6F3C5FCDDBD0111B348-ZmjkEB1lVlLt6d3pZDjeaEtBU8KWyXPq@public.gmane.org>
2014-06-18 12:25 ` GongJinrong
2014-07-02 15:59 ` Thomas Monjalon [this message]
2014-07-03 6:34 ` GongJinrong
[not found] ` <COL402-EAS26784F53BE4DB0028910541B7010-MsuGFMq8XAE@public.gmane.org>
2014-07-03 11:03 ` GongJinrong
[not found] ` <COL402-EAS3344B3BD9A3F216B3176256B7010-MsuGFMq8XAE@public.gmane.org>
2014-07-03 12:05 ` Thomas Monjalon
2014-07-07 9:58 ` xie huawei
[not found] ` <CADpBOO1s8y0n1LHs3K21QkjJ27r7Fiy7wZ_UC++1UO-6fOm7Dg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-07 10:05 ` Thomas Monjalon
-- strict thread matches above, loose matches on Subject: below --
2014-06-13 15:29 John Joyce (joycej)
[not found] ` <7E47E681F1539348840E7A8F1E8AA02E214A68E5-WE/xwOPrfQIoZIgnCEkqtaBKnGwkPULj@public.gmane.org>
2014-06-18 4:02 ` Hiroshi Shimamoto
[not found] ` <7F861DC0615E0C47A872E6F3C5FCDDBD0111A162-ZmjkEB1lVlLt6d3pZDjeaEtBU8KWyXPq@public.gmane.org>
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=3856470.KKoi0bR8VV@xps13 \
--to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=h-shimamoto-ehU+Cx/zZe18UrSeD/g0lQ@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 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).