From: Dario Faggioli <dario.faggioli@citrix.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: edgar.iglesias@xilinx.com, george.dunlap@eu.citrix.com,
Julien Grall <julien.grall@arm.com>,
nd@arm.com, xen-devel@lists.xen.org
Subject: Re: Xen on ARM IRQ latency and scheduler overhead
Date: Sat, 18 Feb 2017 01:47:33 +0100 [thread overview]
Message-ID: <1487378853.6732.106.camel@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1702171559240.9566@sstabellini-ThinkPad-X260>
[-- Attachment #1.1: Type: text/plain, Size: 1623 bytes --]
On Fri, 2017-02-17 at 16:02 -0800, Stefano Stabellini wrote:
> On Fri, 17 Feb 2017, Stefano Stabellini wrote:
> >
> > NODEBUG vwfi=idle credit2 fix cpumasks 4000 2370
> > 4500 3350
> > NODEBUG vwfi=idle credit1 fix cpumasks 3220 2180
> > 4500 4320
>
> Actually those are still the old numbers, sorry!
>
Yeah, I know, I've done the same sooo many times! :-P
> I didn't update the xen
> binary properly. These are the new numbers:
>
> AVG MIN MAX
> WARM MAX
> vwfi=sleep credit2 fix cpumasks 5910 5800 8520
> 6180
> vwfi=sleep credit1 fix cpumasks 4900 4810 6910
> 4980
> vwfi=idle credit2 fix cpumasks 2800 1560 4550
> 4200
> vwfi=idle credit1 fix cpumasks 2800 1610 3420
> 1770
>
> The difference between credit2 and credit1 is smaller now. In fact
> it's
> zero, when vwfi=idle.
>
Ok, cool.
> However, with vwfi=sleep, the larger MAX value is
> a bit worrying.
>
I still think this may be due to the fact that you never stop Credit1's
tick on ARM, which means that, when on Credit1, the system is a lot
more "alive" (e.g., if we were on x86, I'd have said it'd spend less
time in deep C-states, and things like that).
And yes, I still owe you a patch for disabling it.
I'm working on that one. :-)
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-02-18 0:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 0:54 Xen on ARM IRQ latency and scheduler overhead Stefano Stabellini
2017-02-10 8:40 ` Dario Faggioli
2017-02-10 18:32 ` Stefano Stabellini
2017-02-16 12:20 ` Dario Faggioli
2017-02-16 19:52 ` Stefano Stabellini
2017-02-16 23:07 ` Stefano Stabellini
2017-02-17 11:02 ` Dario Faggioli
2017-02-17 19:34 ` Julien Grall
2017-02-17 23:14 ` Stefano Stabellini
2017-02-18 0:02 ` Stefano Stabellini
2017-02-18 0:47 ` Dario Faggioli [this message]
2017-02-17 18:40 ` Dario Faggioli
2017-02-17 19:44 ` Julien Grall
2017-02-17 22:55 ` Stefano Stabellini
2017-02-18 0:59 ` Dario Faggioli
2017-02-20 12:18 ` Punit Agrawal
2017-02-18 0:41 ` Stefano Stabellini
2017-02-20 11:04 ` George Dunlap
2017-02-20 11:40 ` Dario Faggioli
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=1487378853.6732.106.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=edgar.iglesias@xilinx.com \
--cc=george.dunlap@eu.citrix.com \
--cc=julien.grall@arm.com \
--cc=nd@arm.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xen.org \
/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.