From: Bin Ren <bin.ren@gmail.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Andrew Theurer <habanero@us.ibm.com>,
xen-devel@lists.xensource.com, Jon Mason <jdmason@us.ibm.com>
Subject: Re: [PATCH] Network Checksum Removal
Date: Mon, 23 May 2005 22:52:42 +0100 [thread overview]
Message-ID: <8ae7802505052314526e303a24@mail.gmail.com> (raw)
In-Reply-To: <3781733093cae2d97c7358f29073f250@cl.cam.ac.uk>
On 5/23/05, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:
> What happens to CPU usage in dom1 when tx checksumming is disabled?
dom1->dom0: 70.7% id, 0.0% wa, 1.7% hi, 15.0% si
dom1->external: 20.0% id, 0.0% wa, 0.7% hi, 60.0% si
dom1->dom2: 77.7% id, 0.0% wa, 1.0% hi, 9.3% si
>
> Overall though these are the kind of results I would expect. Linux
> usually does csumming at the same time as it has to do a copy anyway,
> and it ends up being limited by memory/L2-cache bandwidth, not the
> extra computation. But the offload extensions haven't cost much to
> implement and there are probably cases where it helps a little.
>
> Maybe I'm being pessimistic though: Can you reproduce the rather more
> impressive speedups that you previously saw, Jon?
>
> -- Keir
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2005-05-23 21:52 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 [this message]
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
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=8ae7802505052314526e303a24@mail.gmail.com \
--to=bin.ren@gmail.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--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.