On Wed, May 20, 2015 at 01:22:18PM -0700, Ethan Jackson wrote:
> Hey guys,
> 
> I know this is a super old thread, but is there any interest in
> reviving it?  On our end we've had a terrible time getting ivshmem
> working until we found this documentation.  I expect future users will
> have the same problem.
> 
> I'd resubmit the patch myself, but I have none of the technical detail
> necessary to make sure the instructions still apply in a dpdk-2.0
> world.  Any volunteers?

Hi Ethan,

I am all for updating the documentation but I haven't looked at IVSHMEM
for quite some time.  I've been testing vhost-cuse/user, so I am clueless
regarding to the needs of dpdk-2.0 or newer qemu.  I hope that you don't
need a patched qemu these days, for example, not sure.

Therefore, I would need that doc too if I had to get IVSHMEM working.

fbl


> Ethan
> 
> On Wed, Sep 3, 2014 at 3:00 PM, Pravin Shelar <pshe...@nicira.com> wrote:
> > On Wed, Sep 3, 2014 at 10:14 AM, Flavio Leitner <f...@redhat.com> wrote:
> >> On Fri, Aug 29, 2014 at 03:54:08PM -0700, Pravin Shelar wrote:
> >>> On Fri, Aug 15, 2014 at 7:07 AM, Polehn, Mike A <mike.a.pol...@intel.com> 
> >>> wrote:
> >>> > Adds documentation on how to run IVSHMEM communication through VM.
> >>> >
> >>> I think INSTALL.DPDK is getting rather large and hard to understand
> >>> with all details.
> >>> so I dropped "Alternative method to get QEMU, download and build from
> >>> OVDK" section.
> >>> We can add this documentation to separate file once vhost support is 
> >>> added.
> >>
> >> It's better to have extra info than no info at all.
> >>
> > I agree, I just wanted to organize it better.
> >
> >> Since all these features are recent, it's hard to find any info out
> >> there, so please keep it.
> >>
> >> fbl
> > _______________________________________________
> > dev mailing list
> > dev@openvswitch.org
> > http://openvswitch.org/mailman/listinfo/dev
> 
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Reply via email to