From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Marco Tizzoni <marco.tizzoni@gmail.com>
Cc: "Fajar A." <fajar@fajar.net>, Fasiha Ashraf <feehapk@yahoo.co.in>,
xen <xen-devel@lists.xensource.com>,
xen-users@lists.xensource.com
Subject: Re: Re: [Xen-users] About profiling xen
Date: Thu, 01 Oct 2009 14:16:56 -0700 [thread overview]
Message-ID: <4AC51C48.40203@goop.org> (raw)
In-Reply-To: <f9611b0f0910011405h416d2372i3a4c7587b84a3fac@mail.gmail.com>
On 10/01/09 14:05, Marco Tizzoni wrote:
>> The clock*event* mechanism is all about setting up timers to raise events.
>>
>> When running paravirtualized, we use Xen-specific versions of both.
>>
> Ok. My problem is granularity. In xen I can't raise events more
> frequently than 1000/s (with timer set to 1000hz).
> Net test softwares such as netperf or hping use setitimer to send
> packet at a fixed rate. On a non-xen box they works fine even with
> 100k packets/sec (i.e. 100k alarms/sec). This can be problematic for
> streaming software and more in general for soft real-time
> applications.
> [...]
> Thanks for your test, I tried and timers work as expected.
OK, good, that takes timers out of the equation.
I guess the problem is the rate at which Xen will context switch between
two domains. Hm.
Does anything change if you pin your domains to different cpus?
J
next prev parent reply other threads:[~2009-10-01 21:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 6:07 About profiling xen Fasiha Ashraf
2009-09-30 6:33 ` [Xen-users] " Marco Tizzoni
2009-09-30 6:37 ` Pasi Kärkkäinen
2009-09-30 6:40 ` Marco Tizzoni
2009-09-30 7:45 ` Marco Tizzoni
2009-09-30 9:06 ` [Xen-devel] " Marco Tizzoni
2009-09-30 14:21 ` Dan Magenheimer
2009-09-30 14:48 ` Re: [Xen-users] " Marco Tizzoni
2009-09-30 16:04 ` Dan Magenheimer
2009-09-30 16:38 ` Marco Tizzoni
2009-09-30 23:23 ` [Xen-devel] " Jeremy Fitzhardinge
2009-10-01 7:35 ` Marco Tizzoni
2009-10-01 20:54 ` Re: [Xen-users] " Jeremy Fitzhardinge
2009-10-01 21:05 ` [Xen-devel] " Marco Tizzoni
2009-10-01 21:16 ` Jeremy Fitzhardinge [this message]
2009-10-01 21:26 ` Re: [Xen-users] " Marco Tizzoni
2009-10-01 21:40 ` Jeremy Fitzhardinge
2009-10-01 21:55 ` [Xen-devel] " Marco Tizzoni
2009-10-01 22:01 ` Re: [Xen-users] " Jeremy Fitzhardinge
2009-10-01 22:20 ` Marco Tizzoni
2009-10-05 11:38 ` Fasiha Ashraf
2009-10-05 20:53 ` Jeremy Fitzhardinge
2009-10-06 5:01 ` [Xen-devel] " Fasiha Ashraf
2009-10-06 5:30 ` Re: [Xen-users] " Jeremy Fitzhardinge
2009-09-30 9:16 ` Fasiha Ashraf
2009-09-30 9:23 ` [Xen-devel] " Pasi Kärkkäinen
2009-10-01 3:41 ` Re: [Xen-users] " Fasiha Ashraf
2009-10-01 9:44 ` [Xen-devel] " Fasiha Ashraf
2009-09-30 23:19 ` Jeremy Fitzhardinge
2009-10-06 7:22 ` Fasiha Ashraf
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=4AC51C48.40203@goop.org \
--to=jeremy@goop.org \
--cc=fajar@fajar.net \
--cc=feehapk@yahoo.co.in \
--cc=marco.tizzoni@gmail.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@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.