From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bin Ren <bin.ren@gmail.com>
Subject: Re: [PATCH] Network Checksum Removal
Date: Tue, 24 May 2005 23:54:50 +0100
Message-ID: <8ae7802505052415546591ad6b@mail.gmail.com>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D1E41B9@liverpoolst.ad.cl.cam.ac.uk>
Reply-To: bin.ren@cl.cam.ac.uk
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E41B9@liverpoolst.ad.cl.cam.ac.uk>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Andrew Theurer <habanero@us.ibm.com>, Rolf Neugebauer <rolf.neugebauer@intel.com>, Jon Mason <jdmason@us.ibm.com>
List-Id: xen-devel@lists.xenproject.org

On 5/24/05, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:
> > What currently I'm really really obssessed is (1)
> > dom1->external with default BVT gives only ~400Mbps (2)
> > dom1->external with my EEVDF scheduler (everything else is
> > exactly the same) gives 610Mbps, very close to
> > dom0->external. With scheduler latency histograms, it seems
> > to be caused by *far too frequent* context switches in BVT.
> > I'm still digging.
>=20
> Have you tried SEDF? I'm itching to make it the default scheduler...
>=20
> Ian

The following numbers are all for dom1->external. Each test runs 50
seconds. dom0/1 shares one CPU.

With default SEDF, throughput is even worse than default BVT: 318Mbps
(down from 410Mbps). I guess, without looking into the source codes,
default SEDF, dom0 and dom1 both get 50% of CPU. I tweaked their CPU
shares and get the followings:

dom1 60%: 493Mbps
dom1 70%: 371Mbps
dom1 80%: 243Mbps

After these tests, dom0 /proc/interrupts is:

           CPU0
 14:      11148        Phys-irq  ide0
 15:          2        Phys-irq  ide1
 16:    1722970        Phys-irq  eth0
 21:          0        Phys-irq  uhci_hcd, uhci_hcd, uhci_hcd, uhci_hcd
256:          5     Dynamic-irq  ctrl-if
257:      92682     Dynamic-irq  timer0
258:         35     Dynamic-irq  console
259:          0     Dynamic-irq  net-be-dbg
260:       4842     Dynamic-irq  blkif-backend
261:    2943112     Dynamic-irq  vif1.0
NMI:          0
LOC:          0
ERR:          0
MIS:          0

dom1 /proc/interrupts is:

           CPU0
256:        474     Dynamic-irq  ctrl-if
257:      45584     Dynamic-irq  timer0
258:       5158     Dynamic-irq  blkif
259:    1097273     Dynamic-irq  eth0
NMI:          0
ERR:          0

SEDF doesn't work out of box and parameter tuning is tricky as for
driver domains.

- Bin