All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zoltan Kiss <zoltan.kiss@linaro.org>
To: zhangleiqiang <zhangleiqiang@gmail.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Question about network performance difference between dom0 and host
Date: Fri, 28 Nov 2014 10:27:14 +0000	[thread overview]
Message-ID: <54784E02.2090605@linaro.org> (raw)
In-Reply-To: <B2F7CCAC-D433-4EB9-8E3A-53948151C58B@gmail.com>

Hi,

I would check whether GRO is enabled under Dom0 or not (ethtool -k 
ethX). Comparing top during test (especially that which context use how 
many percentage), and the number of interrupts per second (grep eth 
/proc/interrupts) would be interesting too.

Regards,

Zoltan

On 28/11/14 02:29, zhangleiqiang wrote:
>
>   I have done some network performance testing under XEN, and found the result which is somehow strange:
>
>     When testing between Hosts (Sender and receiver servers are both booting from kernel-default), running only one netperf process will be enough to reach the upper limit of NIC. However, when testing between Dom0s (Sender and receiver servers are both booting from kernel-xen), we must run more count of netperf process to reach the upper limit of NIC, running only one netperf process the throughout was low. The results using one netperf process are as follows:
>
>           TCP 512    TCP 1460     TCP 4096    TCP 8500
> Hosts:    9134.24    9444.84  9448.05      9447.58    (Mbs)
> Dom0s:    2063.9    3018.95     6561.29         5008.17    (Mbs)
>
>    The question is why one netperf process cannot reach the max throughout of NIC under Dom0 ? I know that Dom0 will have extra overhead when handling interrupt which must be handled by hypervisor first, but I think it is not the reason for it.
>
>    The testing environment details are as follows:
>
>     1. Hardware
>         a. CPU: Intel(R) Xeon(R) CPU E5645 @ 2.40GHz, 2 CPU 6 Cores with Hyper Thread enabled
>         b. NIC: Intel Corporation 82599EB 10-Gigabit SFI/SFP+ Network Connection (rev 01)
>     2. Sofware:
>         a. HostOS: SUSE SLES 11 SP3 (Kernel 3.0.76)
>         b. NIC Driver: IXGBE 3.21.2
>         c. OVS: 2.1.3
>         d. MTU: 1600
>         e. Dom0:6U6G
>     3. Networking Environment:
>         a. All network flows are transmit/receive through OVS
>         b. Sender server and receiver server are connected directly between 10GE NIC
>     4. Testing Tools:
>         a. Sender: netperf
>         b. Receiver: netserver
>
>
> ----------
> zhangleiqiang (Trump)
>
> Best Regards
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      reply	other threads:[~2014-11-28 10:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-28  2:29 Question about network performance difference between dom0 and host zhangleiqiang
2014-11-28 10:27 ` Zoltan Kiss [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=54784E02.2090605@linaro.org \
    --to=zoltan.kiss@linaro.org \
    --cc=xen-devel@lists.xen.org \
    --cc=zhangleiqiang@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.