This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Network buffering of remus

To: brendan@xxxxxxxxx, geoffrey@xxxxxxxxx, dmeyer@xxxxxxxxx, feeley@xxxxxxxxx, norm@xxxxxxxxx, andy@xxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Network buffering of remus
From: Frank Pan <frankpzh@xxxxxxxxx>
Date: Mon, 23 Aug 2010 13:40:44 +0800
Delivery-date: Sun, 22 Aug 2010 22:41:58 -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:content-type; bh=O+vNvasdUC3wB4gX7cln/BppfHGcctFBiR3H+7boSCc=; b=SxlAquMnhuGpz6QBaf/9SaeEr+vRsiKOZQbC0pVrZHiXzqr+sREK+kCQBBDSZhIDyc ydEdEgZ9c/BW8Sg1QmQhcGTB44g7Ln8GqdBUeZokN1Id/yiyF6crL7qWljbhwR5y7ef3 mMatFkSqBUmquJjbsrLN8Q9pupn5w+fcHZ6Rc=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=LJfbl0VJX8yufBscEBUWCagyK10t1FcG3NEYrDm6vBWFSlIiggSicURo8N/REaYtx4 doAP56S0yvSuQeY6kEqWZ/aiAJCmlpZXzIws+ZbTs/iGLIac7/+xDBva2mCc1Ln6smJQ WYjlAwqfKZ2cLN/GIxAqrCJUjJT5txNU5WHxI=
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

I'm doing researches on remus and have a question about its network buffering.

I use the code in the xen unstable tree.
I've run a guest and remus with network buffering(without --no-net),
using the default interval 200ms. Then I ping the guest on the 3rd
machine(other than primary and backup).
I found that the average delay is about 30~50 ms, but I think it
should be larger than 100ms.(due to network buffering, the output
packet could be held for 0~200ms)

Did I make anything wrong with the idea of network buffering? Or did I
make any mistake during the test?

Frank Pan

Computer Science and Technology
Tsinghua University

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>