From: David Becker <becker@cs.duke.edu>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: Diwaker Gupta <diwakergupta@gmail.com>, xen-devel@lists.sourceforge.net
Subject: Re: Xen cluster n/w performance
Date: Mon, 22 Nov 2004 10:28:57 -0500 [thread overview]
Message-ID: <20041122152857.GE1102@cs.duke.edu> (raw)
In-Reply-To: <E1CVpKh-0006kx-00@mta1.cl.cam.ac.uk>
I changed RX_MIN_TARGET in
linux-2.4.27-xenU/arch/xen/drivers/netif/frontend/main.c
and it made no difference at all in the 1500 byte iperf test.
" the number of interrupts per second reported by the dom0 and domU
" in each configuration.
For iperf tcp stream sent from stock linux to xenU
(2.4.27-xenU+RX_MIN_TARGET mod)
1500 MTU: 464 Mbps
interrupts per second seen on xen0:
irq 1: 0 Phys-irq keyboard irq129: 0 Dynamic-irq ctrl-if
irq 14: 0 Phys-irq ide0 irq130: 7473 Dynamic-irq timer
irq 17: 28526 Phys-irq eth0 irq131: 0 Dynamic-irq timer_d
irq 18: 15 Phys-irq aic7xxx irq132: 0 Dynamic-irq console
irq 19: 0 Phys-irq aic7xxx irq133: 0 Dynamic-irq blkif-b
irq128: 0 Dynamic-irq misdire irq134: 1464 Dynamic-irq vif3.0
interrupts per second seen on xenU:
irq128: 0 Dynamic-irq misdire irq131: 0 Dynamic-irq timer_d
irq129: 0 Dynamic-irq ctrl-if irq132: 0 Dynamic-irq blkif
irq130: 5273 Dynamic-irq timer irq133: 5121 Dynamic-irq eth0
552 MTU: 230 Mbps
interrupts per second seen on xen0:
irq 1: 0 Phys-irq keyboard irq129: 0 Dynamic-irq ctrl-if
irq 14: 0 Phys-irq ide0 irq130: 9103 Dynamic-irq timer
irq 17: 19227 Phys-irq eth0 irq131: 0 Dynamic-irq timer_d
irq 18: 10 Phys-irq aic7xxx irq132: 0 Dynamic-irq console
irq 19: 0 Phys-irq aic7xxx irq133: 0 Dynamic-irq blkif-b
irq128: 0 Dynamic-irq misdire irq134: 1804 Dynamic-irq vif3.0
interrupts per second seen on xenU:
irq128: 0 Dynamic-irq misdire irq131: 0 Dynamic-irq timer_d
irq129: 0 Dynamic-irq ctrl-if irq132: 0 Dynamic-irq blkif
irq130: 7264 Dynamic-irq timer irq133: 7158 Dynamic-irq eth0
The e1000 driver is stock, so these are with the default interrupt coalescing
settings.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
prev parent reply other threads:[~2004-11-22 15:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-21 6:37 Xen cluster n/w performance (again!) Diwaker Gupta
2004-11-21 10:52 ` Ian Pratt
2004-11-21 20:10 ` Keir Fraser
2004-11-23 21:32 ` Diwaker Gupta
2004-11-23 22:14 ` Ian Pratt
2004-11-30 21:09 ` David Becker
2004-11-30 21:42 ` Ian Pratt
2004-11-30 23:42 ` David Becker
2004-12-01 9:09 ` Keir Fraser
2004-12-03 21:23 ` David Becker
2004-11-22 15:28 ` David Becker [this message]
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=20041122152857.GE1102@cs.duke.edu \
--to=becker@cs.duke.edu \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=diwakergupta@gmail.com \
--cc=xen-devel@lists.sourceforge.net \
/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.