From: Nivedita Singhvi <niv@us.ibm.com>
To: bin.ren@cl.cam.ac.uk
Cc: xen-devel@lists.xensource.com,
Andrew Theurer <habanero@us.ibm.com>,
Jon Mason <jdmason@us.ibm.com>
Subject: Re: [PATCH] Network Checksum Removal
Date: Mon, 23 May 2005 14:12:24 -0700 [thread overview]
Message-ID: <42924738.9020106@us.ibm.com> (raw)
In-Reply-To: <8ae780250505231255a0cea3b@mail.gmail.com>
Bin Ren wrote:
> 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.
Yeah, if you want to do anything network intensive, 128MB is just
not enough - you really need more memory in your system.
> 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)
iperf is a directional send test, correct?
i.e. is dom1 -> dom0 perf the same as dom0 -> dom1 for you?
thanks,
Nivedita
next prev parent reply other threads:[~2005-05-23 21:12 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-20 23:30 [PATCH] Network Checksum Removal Jon Mason
2005-05-21 14:53 ` Keir Fraser
2005-05-21 19:16 ` Keir Fraser
2005-05-21 21:49 ` Jon Mason
2005-05-23 15:29 ` Andrew Theurer
2005-05-23 15:31 ` Bin Ren
2005-05-23 15:47 ` Andrew Theurer
2005-05-23 15:56 ` Bin Ren
2005-05-23 16:06 ` Bin Ren
2005-05-23 16:16 ` Jon Mason
2005-05-23 16:36 ` Bin Ren
2005-05-23 17:54 ` Keir Fraser
2005-05-23 18:08 ` Bin Ren
2005-05-23 18:18 ` Jon Mason
2005-05-23 18:43 ` Keir Fraser
2005-05-23 18:53 ` Bin Ren
2005-05-23 19:55 ` Bin Ren
2005-05-23 20:13 ` Keir Fraser
2005-05-23 20:20 ` Jon Mason
2005-05-23 21:52 ` Bin Ren
2005-05-23 21:58 ` Jon Mason
2005-05-23 22:05 ` Bin Ren
2005-05-23 22:41 ` Jon Mason
2005-05-23 21:12 ` Nivedita Singhvi [this message]
2005-05-23 21:48 ` Bin Ren
2005-05-23 23:55 ` Rolf Neugebauer
2005-05-24 0:38 ` Bin Ren
-- strict thread matches above, loose matches on Subject: below --
2005-05-23 20:22 Ian Pratt
2005-05-23 20:38 ` Keir Fraser
2005-05-23 20:44 ` Jon Mason
2005-05-23 21:01 ` Bin Ren
2005-05-23 21:09 ` Andrew Theurer
2005-05-23 20:26 Ian Pratt
2005-05-23 23:59 Ian Pratt
2005-05-24 16:12 ` Jon Mason
2005-05-24 20:45 ` Andrew Theurer
2005-05-25 14:38 ` Andrew Theurer
2005-05-24 1:22 Ian Pratt
2005-05-24 1:35 ` Bin Ren
2005-05-24 22:54 ` Bin Ren
2005-05-25 16:48 Ian Pratt
2005-05-25 17:13 ` Jon Mason
2005-05-25 18:19 ` Nivedita Singhvi
2005-05-25 20:06 Ian Pratt
2005-05-25 21:14 ` Keir Fraser
2005-05-25 21:35 ` Jon Mason
2005-05-25 21:40 ` Keir Fraser
2005-05-25 23:41 ` Jon Mason
2005-05-26 8:07 ` Keir Fraser
2005-05-26 13:37 ` Jon Mason
2005-05-25 21:38 ` Cédric Schieli
2005-05-25 21:47 ` Keir Fraser
2005-05-25 21:54 ` Keir Fraser
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=42924738.9020106@us.ibm.com \
--to=niv@us.ibm.com \
--cc=bin.ren@cl.cam.ac.uk \
--cc=habanero@us.ibm.com \
--cc=jdmason@us.ibm.com \
--cc=xen-devel@lists.xensource.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.