DPDK announcements
 help / color / mirror / Atom feed
From: "St Leger, Jim" <jim.st.leger@intel.com>
To: "announce@dpdk.org" <announce@dpdk.org>
Cc: "Nehama, Dana" <dana.nehama@intel.com>
Subject: [dpdk-announce] FYI: DPDK Accelerated vSwitch Projects
Date: Tue, 25 Nov 2014 20:42:48 +0000	[thread overview]
Message-ID: <00B2C372B6E6DA4FB04934511BF0564A3E4CCDAC@FMSMSX114.amr.corp.intel.com> (raw)

FYI.
An update from the Intel team on our two vSwitch efforts and the move now to converge solely on the mainline community Open vSwitch project (now that ovs.org has adopted the DPDK acceleration model that was proven out via the 01.org "OVDK" project.)
Jim

-----Original Message-----
From: Dpdk-ovs [mailto:dpdk-ovs-bounces@lists.01.org] On Behalf Of dpdk-ovs-request@lists.01.org
Sent: Tuesday, November 25, 2014 1:00 PM
To: dpdk-ovs@lists.01.org
Subject: Dpdk-ovs Digest, Vol 17, Issue 25

Send Dpdk-ovs mailing list submissions to
	dpdk-ovs@lists.01.org

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.01.org/mailman/listinfo/dpdk-ovs
or, via email, send a message with subject or body 'help' to
	dpdk-ovs-request@lists.01.org

You can reach the person managing the list at
	dpdk-ovs-owner@lists.01.org

When replying, please edit your Subject line so it is more specific than "Re: Contents of Dpdk-ovs digest..."


Today's Topics:

   1. Clarification on Intel Support for the Intel DPDK Accelerated
      Open vSwitch (OVDK) (Gray, Mark D)


----------------------------------------------------------------------

Message: 1
Date: Tue, 25 Nov 2014 10:55:03 +0000
From: "Gray, Mark D" <mark.d.gray@intel.com>
To: "dpdk-ovs@lists.01.org" <dpdk-ovs@lists.01.org>
Subject: [Dpdk-ovs] Clarification on Intel Support for the Intel DPDK
	Accelerated Open vSwitch (OVDK)
Message-ID:
	<738D45BC1F695740A983F43CFE1B7EA92D790E6E@IRSMSX102.ger.corp.intel.com>
	
Content-Type: text/plain; charset="us-ascii"

Hi,

As part of its commitment to SDN and NFV, Intel is an active participant in several open source and open standards projects. Until recently, Intel made contributions to two virtual switch community projects: Open vSwitch (OVS) and Intel(r) DPDK Accelerated Open vSwitch (OVDK). OVDK successfully demonstrated the huge advantage of DPDK for data packet acceleration and today DPDK is well received for high performing virtual switches and routers. Now, with the capabilities of DPDK incorporated into the mainstream OVS project, Intel is ceasing investments around OVDK and instead focusing efforts around OVS with DPDK-netdev, and advancing hardware acceleration.

Q&A
------------------------------------------------------------

Can I still use OVDK?
Yes. However Intel is migrating to Open vSwitch version 2.4, which includes DPDK-netdev in user space (currently available as an experimental feature Open vSwitch version 2.3).

How long will Intel continue to maintain the OVDK project?
Maintenance, which includes integration of patches, nightly builds, mailing list support, and bug fixing on a best-effort basis, will continue until July 1, 2015. However, there will be no further enhancements, effective immediately.

What are intel plans for OVS?
Intel will focus its effort in advancing hardware acceleration when using OVS with DPDK-netdev 

Will Intel continue to make improvements to the DPDK?
Yes. Updates will be available in the DPDK download available at www.dpdk.org and incorporated into future Open vSwitch features. For more information about the DPDK, visit www.dpdk.org.  

------------------------------------------------------------

Regards, 

Mark


------------------------------

Subject: Digest Footer

_______________________________________________
Dpdk-ovs mailing list
Dpdk-ovs@lists.01.org
https://lists.01.org/mailman/listinfo/dpdk-ovs


------------------------------

End of Dpdk-ovs Digest, Vol 17, Issue 25
****************************************

                 reply	other threads:[~2014-11-25 20:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=00B2C372B6E6DA4FB04934511BF0564A3E4CCDAC@FMSMSX114.amr.corp.intel.com \
    --to=jim.st.leger@intel.com \
    --cc=announce@dpdk.org \
    --cc=dana.nehama@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).