From: "Gray, Mark D" <mark.d.gray@intel.com>
To: "Loftus, Ciara" <ciara.loftus@intel.com>,
"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 09:22:14 +0000 [thread overview]
Message-ID: <738D45BC1F695740A983F43CFE1B7EA943921158@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <74F120C019F4A64C9B78E802F6AD4CC24F7D3872@IRSMSX106.ger.corp.intel.com>
> >
> > 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.
>
There seems to be a general direction in DPDK to move everything under a PMD
if we make the main interface into DPDK a pmd, we can simplify the OVS code base
and make it easier to add additional port-types in the future without
modifying OVS code.
prev parent reply other threads:[~2015-12-02 9:22 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
2015-12-02 9:22 ` Gray, Mark D [this message]
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=738D45BC1F695740A983F43CFE1B7EA943921158@IRSMSX108.ger.corp.intel.com \
--to=mark.d.gray@intel.com \
--cc=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).