From: Flavio Leitner <fbl@sysclose.org>
To: Marcel Apfelbaum <marcel@redhat.com>
Cc: qemu list <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [wiki] New wiki page - vhost-user setup with ovs/dpdk backend
Date: Thu, 17 Sep 2015 09:46:27 -0300 [thread overview]
Message-ID: <20150917124627.GA2192@x240.home> (raw)
In-Reply-To: <55FA9124.7020606@redhat.com>
On Thu, Sep 17, 2015 at 01:08:36PM +0300, Marcel Apfelbaum wrote:
> On 09/16/2015 08:44 PM, Flavio Leitner wrote:
> >On Thu, Sep 10, 2015 at 10:51:19PM +0300, Marcel Apfelbaum wrote:
> >>Hi,
> >>
> >>The page describes how to setup an environment that allows testing/developing
> >>vhost-user using ovs (with dpdk) as backend.
> >>
> >>A regular pc machine can be used, no need for several hosts, a 'dpdk enabled' NIC or 1G huge-pages.
> >>
> >>The goal is to connect guests' virtio-net devices having vhost-user backend to OVS dpdkvhostuser ports
> >>and be able to run any kind of network traffic between them.
> >>
> >>The page can be found at:
> >>http://wiki.qemu.org/Features/vhost-user-ovs-dpdk
> >>
> >>I want to keep it as simple as possible.
> >>If you see steps that can be skipped or unneeded configuration please let me know
> >>or feel free to update the page.
> >
> >I gave a quick look and found couple issues. It seems to be missing
> >the installing steps for qemu. Also the eventfd_link module is only
> >needed for vhost-cuse, so you don't need to build/install/load at all.
> Hi Flavio,
> Thank you for reviewing the document!
>
> For some reason I thought we still need eventfd_link to notify the guests
> when new packets arrive. Indeed we don't need this anymore, I updated the wiki page.
We use the one provided by kernel. The eventfd_link on DPDK is special for
vhost-cuse:
https://github.com/openvswitch/ovs/blob/master/INSTALL.DPDK.md#dpdk-vhost-cuse-prerequisites
> Regarding QEMU, can you please point me to the missing setup steps?
> (I think I already took care of them, anyway I want to be sure)
Yup, I missed that you are running qemu from the builddir, not from
the system, so you don't need to install it.
Thanks again,
fbl
next prev parent reply other threads:[~2015-09-17 12:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 19:51 [Qemu-devel] [wiki] New wiki page - vhost-user setup with ovs/dpdk backend Marcel Apfelbaum
2015-09-16 17:44 ` Flavio Leitner
2015-09-17 10:08 ` Marcel Apfelbaum
2015-09-17 12:46 ` Flavio Leitner [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-09-18 17:16 chandrasekar kannan
2015-09-20 9:13 ` Marcel Apfelbaum
[not found] <CAMy83uR2UDVu_7dxjRzzEj0EVJipA6QnyovmTOKDAT-4BWs67g@mail.gmail.com>
[not found] ` <55FFBEF6.3020000@redhat.com>
2015-09-21 18:34 ` Marcel Apfelbaum
2015-09-22 5:43 ` Star Chang
2015-09-22 7:06 ` Marcel Apfelbaum
2015-09-22 14:17 ` Alexandre DERUMIER
2015-09-22 14:53 ` Marcel Apfelbaum
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=20150917124627.GA2192@x240.home \
--to=fbl@sysclose.org \
--cc=marcel@redhat.com \
--cc=qemu-devel@nongnu.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).