From: "Loftus, Ciara" <ciara.loftus@intel.com>
To: "Traynor, Kevin" <kevin.traynor@intel.com>,
Flavio Leitner <fbl@sysclose.org>
Cc: "dev@openvswitch.org" <dev@openvswitch.org>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [ovs-dev] OVS with DPDK Meetup notes
Date: Wed, 2 Dec 2015 00:54:12 +0000 [thread overview]
Message-ID: <74F120C019F4A64C9B78E802F6AD4CC24F7D3872@IRSMSX106.ger.corp.intel.com> (raw)
In-Reply-To: <BC0FEEC7D7650749874CEC11314A88F745316D2D@IRSMSX104.ger.corp.intel.com>
> >
> > On Thu, Nov 26, 2015 at 05:56:08PM +0000, Traynor, Kevin wrote:
> > > Hi All,
> > >
> > > Just wanted to post some summary notes on the recent OVS with DPDK
> Meetup
> > we
> > > had after the OVS conference. Thanks to everyone for the often lively
> > discussion.
> > > I've collated and condensed Maryam's notes (Thank you Maryam) with
> my own.
> > > Corrections and additions are welcome.
> >
> > Thanks for having organized the event and for the good notes.
> >
> >
> > > Usability
> > > ==========
> > > * Single binary for OVS/OVS with DPDK and static vs. dynamic linking
> > > - Discussion around deployment and what the best model is.
> > > - Flavio has posted a mail on this
> > > http://openvswitch.org/pipermail/dev/2015-November/062599.html
> >
> > Let us know if you find a performance difference between static vs
> > dynamic linking. We might be able to accommodate both options in
> > the same spec, but it seems we should go with shared linking only
> > to keep it simple for now.
> >
>
> Yes, will do. I seem to recall from when we looked at this on a previous
> project it was a few hundred kpps but it was a long time ago, so I'm not
> certain how many.
>
> >
> > > Features
> > > ========
> > > * Multiqueue vhost-user
> > > - Looks really promising - will help us scale out performance to the VM.
> >
> > I see that vhost PMD is moving and if it gets accepted, it would
> > be a nice clean up for OVS. Do you know if there is someone working
> > on this already?
>
> I agree, it should simplify the code a lot. Ciara reviewed it and did a
> quick integration to see if the api would work. The patch was churning quite
> a bit, so we decided to hold off doing any more work with it for the time
> being.
Correct, the vHost PMD really cleans things up and removes the need for a lot of code in netdev-dpdk. The netdev_class for phy ports and vhost-user ports could be pretty much the same, except for the construct functions.
>
> >
> > > * dpdkr/ivshmem
> > > - Still useful. Check/Update documentation to ensure limitations are
> > clear.
> >
> > Yeah, same thing here.
> >
> > Thanks,
> > fbl
next prev parent reply other threads:[~2015-12-02 0:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BC0FEEC7D7650749874CEC11314A88F74530E8EB@IRSMSX104.ger.corp.intel.com>
2015-11-27 14:20 ` [dpdk-dev] FW: " Mcnamara, John
[not found] ` <20151130235111.GC8825@x240.home>
2015-12-01 11:11 ` [dpdk-dev] [ovs-dev] " Traynor, Kevin
2015-12-02 0:54 ` Loftus, Ciara [this message]
2015-12-02 9:22 ` Gray, Mark D
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=74F120C019F4A64C9B78E802F6AD4CC24F7D3872@IRSMSX106.ger.corp.intel.com \
--to=ciara.loftus@intel.com \
--cc=dev@dpdk.org \
--cc=dev@openvswitch.org \
--cc=fbl@sysclose.org \
--cc=kevin.traynor@intel.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).