From: John Byrne <john.l.byrne@hp.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Direct I/O performance: direct interrupts to running domU?
Date: Wed, 15 Nov 2006 18:56:22 -0800 [thread overview]
Message-ID: <455BD356.5010206@hp.com> (raw)
Hi,
I'm testing performance of a NIC assigned directly to a domU. (xen-3.0.3
x86_64)
After your help straightening out the problems with my test environment,
my netperf throughput numbers were close to base Linux (generally with
0.5%); however, when I did the netperf transaction tests, the numbers on
Xen (either dom0 and domU) were 10-20% lower than the base Linux
depending on the test parameters. Since this linear transaction test
would be very sensitive to the latency/path-length involved in the
interrupt delivery, I'm making the assumption, for the moment, that this
is the problem without cranking up xenoprof/oprofile to prove it.
One of the questions that came up in a discussion was whether it might
be technically possible to have interrupts delivered directly to a
running domain without the hypervisor overhead. This would presumably
involve some additional overhead at the time the hypervisor switched
domains, but it might be a worthwhile trade-off.
Thanks,
John Byrne
next reply other threads:[~2006-11-16 2:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 2:56 John Byrne [this message]
2006-11-16 3:05 ` Direct I/O performance: direct interrupts to running domU? Mark Williamson
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=455BD356.5010206@hp.com \
--to=john.l.byrne@hp.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.