[Xen-devel] About ping latency in SR-IOV

To:	"Rose, Gregory V" <gregory.v.rose@xxxxxxxxx>, "Dong, Eddie" <eddie.dong@xxxxxxxxx>
Subject:	[Xen-devel] About ping latency in SR-IOV
From:	XiaYubin <xiayubin@xxxxxxxxx>
Date:	Fri, 29 Oct 2010 16:31:09 +0800
Cc:	xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Fri, 29 Oct 2010 01:32:26 -0700
Dkim-signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:from:date :message-id:subject:to:cc:content-type; bh=R+eEb3ZdnnPq/Ykv0iIorGN2bul0Olx0S+ElhJ3brls=; b=Id0c+6WyISixmu4PRXidPO8bAwHothNoJNu9/6kiftRdHNFngnXHwEuElUF30gmceY Ffgdm09FQofRk33l3HQhnJdatIbCKyWtwUw+AeNRVOC6zqvAP0+T77Bx1YkO0S6N/O4C Ke0Z7VEwRHeKGn3w86qBkl0v5/d+qOg/GsMn0=
Domainkey-signature:	a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:cc:content-type; b=jQKJaGCrHyE1lTcl1yF4uD+cMn9dgrOhPW/Snp4QCPGJLvHyU367YTdLk4BgzGEbxI E9BpYh2sMo0OGL5Uiem1q9/pKHSrF4+NW1Paazaj8sxHfgOG3y8knk06Wif7ddD3L4g0 VoPY4b6xHJ2+WOP3YEjS9NtRNqc1qfmER95ko=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

Hi, Greg, Eddie,

I found that in SR-IOV + HVM environment, ping latency depends on ping interval.

The NIC is Intel 82576 (1000Mbps), server uses xen-4.0.1, domain-0 is
kernel-2.6.32
and HVM is kernel-2.6.31. The server and client are connected through
a 1000Mbps switch.

The data is as following:

# ping -i 1 192.168.0.21

PING 192.168.0.21 (192.168.0.21) 56(84) bytes of data.
64 bytes from 192.168.0.21: icmp_seq=1 ttl=64 time=0.117 ms
64 bytes from 192.168.0.21: icmp_seq=2 ttl=64 time=0.100 ms
64 bytes from 192.168.0.21: icmp_seq=3 ttl=64 time=0.102 ms
64 bytes from 192.168.0.21: icmp_seq=4 ttl=64 time=0.100 ms
64 bytes from 192.168.0.21: icmp_seq=5 ttl=64 time=0.105 ms

--- 192.168.0.21 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3998ms
rtt min/avg/max/mdev = 0.100/0.104/0.117/0.014 ms

# ping -i 0 192.168.0.21

PING 192.168.0.21 (192.168.0.21) 56(84) bytes of data.
64 bytes from 192.168.0.21: icmp_seq=1 ttl=64 time=0.114 ms
64 bytes from 192.168.0.21: icmp_seq=2 ttl=64 time=0.418 ms
64 bytes from 192.168.0.21: icmp_seq=3 ttl=64 time=0.455 ms
64 bytes from 192.168.0.21: icmp_seq=4 ttl=64 time=0.456 ms
64 bytes from 192.168.0.21: icmp_seq=5 ttl=64 time=0.455 ms

--- 192.168.0.21 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 1ms
rtt min/avg/max/mdev = 0.114/0.379/0.456/0.135 ms, ipg/ewma 0.400/0.252 ms

The ping latency of PF (in domain-0) is about 0.08ms in both tests.
Is this caused by something related to interrupt throttle configuration?
If so, can we adjust its threshold?

Thanks!

--
Yubin

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

WARNING - OLD ARCHIVES

xen-devel

[Xen-devel] About ping latency in SR-IOV