From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bin Ren Subject: Re: [PATCH] Network Checksum Removal Date: Mon, 23 May 2005 20:55:47 +0100 Message-ID: <8ae780250505231255a0cea3b@mail.gmail.com> References: <20050520233015.GA26305@us.ibm.com> <8ae78025050523085662a94019@mail.gmail.com> <8ae7802505052309067d88f174@mail.gmail.com> <200505231116.16964.jdmason@us.ibm.com> <8ae7802505052309362c2fb00e@mail.gmail.com> <32fa5a4ad70f86ee5637d30ffc890017@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: In-Reply-To: <32fa5a4ad70f86ee5637d30ffc890017@cl.cam.ac.uk> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Andrew Theurer , xen-devel@lists.xensource.com, Jon Mason List-Id: xen-devel@lists.xenproject.org I've added the support for ethtools. By turning on and off netfront checksum offloading, I'm getting the following throughput numbers, using iperf. Each test was run three times. CPU usages are quite similar in two cases ('top' output). Looks like checksum computation is not a major overhead in domU networking. dom0/1/2 all have 128M memory. dom0 has e1000 tx checksum offloading turned= on. With Tx checksum on: dom1->dom2: 300Mb/s (dom0 cpu maxed out by software interrupts) dom1->dom0: 459Mb/s (dom0 cpu 80% in SI, dom1 cpu 20% in SI) dom1->external: 439Mb/s (over 1Gb/s ethernet) (dom0 cpu 50% in SI, dom1 60% in SI) With Tx checksum off: dom1->dom2: 301Mb/s dom1->dom0: 454Mb/s dom1->externel: 437Mb/s (over 1Gb/s ethernet) On 5/23/05, Keir Fraser wrote: >=20 > On 23 May 2005, at 17:36, Bin Ren wrote: >=20 > > Keir has removed 'SET_ETHTOOL_OPS(dev, &network_ethtool_ops);' from > > your patch. The operations are not supported. >=20 > Ah, I thought that was just testing infrastructure. I'll take a patch > to add the ethtool ops back in. >=20 > Bin -- does your domain0 traffic get delivered via the bridge device or > via the new vif0.0/veth0 that I added? If the former you might want to > try updating your /etc/xen/scripts/network script. Although delivery > via the bridge ought to work... >=20 > -- Keir >=20 >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >