All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dfaggioli@suse.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Ryan Thibodeaux <thibodux@gmail.com>
Cc: jgross@suse.com, oleksandr_andrushchenko@epam.com,
	"luca.abeni" <luca.abeni@santannapisa.it>,
	linux-kernel@vger.kernel.org, ryan.thibodeaux@starlab.io,
	xen-devel@lists.xenproject.org, tglx@linutronix.de
Subject: Re: [PATCH] x86/xen: Add "xen_timer_slop" command line option
Date: Mon, 25 Mar 2019 11:36:00 +0100	[thread overview]
Message-ID: <8eec0949bac18d8ee6f151027ff68de9827f143d.camel__17983.1970877544$1553510268$gmane$org@suse.com> (raw)
In-Reply-To: <20190324180724.GA4400@nat-wireless-guest-reg-153-50.bu.edu>


[-- Attachment #1.1: Type: text/plain, Size: 1940 bytes --]

On Sun, 2019-03-24 at 14:07 -0400, Boris Ostrovsky wrote:
> On Sat, Mar 23, 2019 at 08:00:52AM -0400, Ryan Thibodeaux wrote:
> > This test system was configured to use a TSC clocksource, disabled
> > C states, and lowered the timer slop. I am not claiming the timer
> > slop change was solely responsible for the best results.
> 
> How can we then be sure that the proposed change will indeed provide
> some sort of benefit?
> 
> Were there any other changes between your tests to think that slop
> time modification may not be responsible for better results?
> 
FWIW, in mine and Luca's experiments, changing lowering both timer_slop
in Xen and TIMER_SLOP in Linux, improved latency dramatically, without
any other change.

We also tried _only_ playing with the Xen tunable (as there's a Xen
boot parameter for it already) but that wasn't enough. It was only when
we also tuned TIMER_SLOP in Linux's Xen clockevent device that we got
decent numbers (i.e., comparable to KVM ones).

Reason why we had not share these results yet was that we were still
"polishing" them, and because we also found a couple of other issues,
and we were trying to understand them better, before sending anything
out. But those other issues were --although still about achieving low
latencies-- orthogonal from this, and lowering the default slop is
absolute prerequisite for even talking about having a reasonable vcpu
response time.

A patch like this one, was something we were thinking to submit ourself
sooner or later (backed up by our results). Personally, in addition to
making the value tunable, which I think is a good thing, I also would
lower the default.

Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Software Engineer @ SUSE https://www.suse.com/

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  parent reply	other threads:[~2019-03-25 10:36 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22 18:29 [PATCH] x86/xen: Add "xen_timer_slop" command line option thibodux
2019-03-22 22:10 ` Boris Ostrovsky
2019-03-23  2:58   ` Dario Faggioli
2019-03-23  2:58   ` Dario Faggioli
2019-03-23 10:41     ` luca abeni
2019-03-25 12:05       ` luca abeni
2019-03-25 13:43         ` Boris Ostrovsky
2019-03-25 14:07           ` luca abeni
2019-03-25 14:07           ` luca abeni
2019-03-25 14:11           ` Ryan Thibodeaux
2019-03-25 17:36             ` Ryan Thibodeaux
2019-03-25 17:36             ` Ryan Thibodeaux
2019-03-25 18:31             ` Boris Ostrovsky
2019-03-25 18:31             ` Boris Ostrovsky
2019-03-25 14:11           ` Ryan Thibodeaux
2019-03-26  9:13           ` Dario Faggioli
2019-03-26  9:13           ` Dario Faggioli
2019-03-26 11:12             ` luca abeni
2019-03-26 11:41               ` Ryan Thibodeaux
2019-03-26 11:41               ` Ryan Thibodeaux
2019-03-26 11:12             ` luca abeni
2019-03-26 23:21             ` Boris Ostrovsky
2019-03-27 10:00               ` Ryan Thibodeaux
2019-03-27 10:00               ` Ryan Thibodeaux
2019-03-27 14:46                 ` Boris Ostrovsky
2019-03-27 14:59                   ` Ryan Thibodeaux
2019-03-27 14:59                   ` Ryan Thibodeaux
2019-03-27 15:19                   ` Dario Faggioli
2019-03-27 15:19                   ` Dario Faggioli
2019-03-27 14:46                 ` Boris Ostrovsky
2019-03-26 23:21             ` Boris Ostrovsky
2019-03-25 13:43         ` Boris Ostrovsky
2019-03-25 12:05       ` luca abeni
2019-03-23 10:41     ` luca abeni
2019-03-23 12:00   ` Ryan Thibodeaux
2019-03-23 12:00     ` Ryan Thibodeaux
2019-03-24 18:07     ` Boris Ostrovsky
2019-03-24 18:07     ` Boris Ostrovsky
2019-03-25 10:36       ` Dario Faggioli
2019-03-25 10:36       ` Dario Faggioli [this message]
2019-03-22 22:10 ` Boris Ostrovsky
2019-04-24 18:47 ` Boris Ostrovsky
2019-04-24 18:47   ` [Xen-devel] " Boris Ostrovsky
2019-04-24 18:47 ` Boris Ostrovsky
  -- strict thread matches above, loose matches on Subject: below --
2019-03-22 18:29 thibodux

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='8eec0949bac18d8ee6f151027ff68de9827f143d.camel__17983.1970877544$1553510268$gmane$org@suse.com' \
    --to=dfaggioli@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.abeni@santannapisa.it \
    --cc=oleksandr_andrushchenko@epam.com \
    --cc=ryan.thibodeaux@starlab.io \
    --cc=tglx@linutronix.de \
    --cc=thibodux@gmail.com \
    --cc=xen-devel@lists.xenproject.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.