DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jun Xiao <jun.xiao@cloudnetengine.com>
To: "Gray, Mark D" <mark.d.gray@intel.com>
Cc: dev <dev@dpdk.org>, discuss <discuss@openvswitch.org>
Subject: Re: [dpdk-dev] [ovs-discuss] vswitches performance comparison
Date: Wed, 22 Jul 2015 02:48:51 +0800	[thread overview]
Message-ID: <9D0E6ED2-6171-4EF5-AD21-01B1844B5136@cloudnetengine.com> (raw)
In-Reply-To: <738D45BC1F695740A983F43CFE1B7EA92E2BEFD4@IRSMSX108.ger.corp.intel.com>



> On Jul 22, 2015, at 2:36 AM, Gray, Mark D <mark.d.gray@intel.com> wrote:
> 
> 
>> 
>> I'd like to hope that's my methodology problem, but I just follow the
>> installation guide without any customization.
>> 
>> Hi Mark, do you have any performance data share with us? Maybe we are
>> using different type of workloads, like I mentioned I am using typical data
>> center workload, I guess you are talking about NFV type of workload?
> 
> The number getting floated around on the mailing list recently is 16.5Mpps
> for phy-phy. However, I don't think we have any iperf data off-hand for your
> usecase. When we test throughput into the vm we usually generate the traffic externally
> and send NIC->OVS->VM->OVS->NIC. This is a little different to your setup.
> 

I guess pmd driver is used inside VM in that case, right?
> I do know, however, that ovs-dpdk typically has a much larger throughput than
> the kernel space datapath.
> 

I'd like to say it depends on workloads, for small/medium packet size workload, that's definitely true, while for TSO size workload, it's not that obvious (or worse) as data path overheads are amortized and H/W can be leveraged.
> Have you seen this? https://wiki.opnfv.org/characterize_vswitch_performance_for_telco_nfv_use_cases
> 

Thanks for the pointer, I'll try later.
>> 
>> Thanks,
>> Jun

  reply	other threads:[~2015-07-21 18:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-21 18:00 [dpdk-dev] " Jun Xiao
2015-07-21 18:14 ` [dpdk-dev] [ovs-discuss] " Gray, Mark D
2015-07-21 18:28   ` Jun Xiao
2015-07-21 18:36     ` Gray, Mark D
2015-07-21 18:48       ` Jun Xiao [this message]
2015-07-22  8:06         ` Gray, Mark D
2015-07-21 21:02 ` [dpdk-dev] " Stephen Hemminger
2015-07-22  8:07   ` 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=9D0E6ED2-6171-4EF5-AD21-01B1844B5136@cloudnetengine.com \
    --to=jun.xiao@cloudnetengine.com \
    --cc=dev@dpdk.org \
    --cc=discuss@openvswitch.org \
    --cc=mark.d.gray@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).