From: "Jun Xiao" <jun.xiao@cloudnetengine.com>
To: "dev" <dev@dpdk.org>
Subject: [dpdk-dev] CloudNetEngine vSwitch technical preview is available!
Date: Mon, 20 Jul 2015 08:37:19 +0800 [thread overview]
Message-ID: <----Tc------lRRzc$305d3246-8ed0-4823-a35d-cb5cf41a0146@cloudnetengine.com> (raw)
We are very excited to announce that CloudNetEngine vswitch is available for
technical preview!
CloudNetEngine vswitch perfectly bridges the gaps of performance, efficiency and
full feature requirements which existing vswitches simply cannot provide.
CloudNetEngine vswitch is based on some great open source projects OVS,
DPDK, NPF, and more importantly with our own very unique proprietary network
stack to support following important features:
- H/W and S/W TSO and CSUM support for both native and overlay networks.
- Distributed stateful firewall per virtual port with powerful BPF JIT
engine.
- Patent-pending approach for tunneling acceleration, which achieves the best
VXLAN performance in the industry.
• Network traffic shapping for virtual ports.
• Very efficient and user friendly userspace vswitch traffic sniffing.
One quick reference on performance data, on our setup (Xeon E5-2620 v3 2.40GHz
+ Intel 82599 NICs), if we use VMs’ TCP traffic to drive to NIC's line rate,
CloudNetEngine vswitch can save more than 1.5 logical core than native kernel
OVS on *EACH* hypervisor! You can imagine how amazing saving it would be for
your clouds.
(Note: the TCP test is already the best case for native kernel OVS, and the
difference is much more significant for small/medium packet size traffic.)
We encourage you to try it out in your own setup, please send evaluation
requests to info@cloudnetengine.com. (Note: we only accept requests with
corporate emails for now)
Cheers!
Jun Xiao
www.cloudnetengine.com
reply other threads:[~2015-07-20 0:37 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='----Tc------lRRzc$305d3246-8ed0-4823-a35d-cb5cf41a0146@cloudnetengine.com' \
--to=jun.xiao@cloudnetengine.com \
--cc=dev@dpdk.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).