All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] tools/libxc: Avoid hypercalls for cacheflush on x86
Date: Tue, 4 Mar 2014 11:22:08 +0000	[thread overview]
Message-ID: <5315B760.3080408@citrix.com> (raw)
In-Reply-To: <1393895670.10902.7.camel@hastur.hellion.org.uk>

On 04/03/14 01:14, Ian Campbell wrote:
> On Mon, 2014-03-03 at 16:22 +0000, Ian Jackson wrote:
>> Andrew Cooper writes ("[PATCH] tools/libxc: Avoid hypercalls for cacheflush on x86"):
>>> XEN_DOMCTL_cacheflush hypercalls are -ENOSYS on x86.  As domain
>>> creation/migration is already very hypercall-heavy, avoid making extra
>>> redundant hypercalls
>> Surely this should be done by moving the relevant code to an
>> arm-specific file, not by #ifdeffery.
> I think it is very debatable that sort-circuiting a single ENOSYS
> hypercall in the tools is even worth it at all. "very hypercall heavy"
> doesn't cut it as a rationale IMHO. Unless an actual demonstrable
> improvement is seen, perhaps over a larger series removing a large
> number of so called redundant calls, it's just an additional source of
> confusion (due to gating at multiple levels) as far as I'm concerned.
>
> Ian.
>

For booting a single guest, noone will notice.  Booting 10 or more at a
time however is very different.

XenServer, along with all other virtualisation platforms live in a world
where "Net time to boot $N guests" (where N is measured in hundreds) is
an important quantity, and needless overhead from things like this cause
dom0 needless load that it would rather do without.

I should say that I have not done any performance metrics on this - as
noted in the patch I stumbled upon it with valgrind.

~Andrew

  reply	other threads:[~2014-03-04 11:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-03 14:37 [PATCH] tools/libxc: Avoid hypercalls for cacheflush on x86 Andrew Cooper
2014-03-03 16:19 ` David Vrabel
2014-03-03 16:22 ` Ian Jackson
2014-03-04  1:14   ` Ian Campbell
2014-03-04 11:22     ` Andrew Cooper [this message]
2014-03-11 11:31       ` Ian Campbell
2014-03-04  1:18   ` Ian Campbell
2014-03-04  9:24 ` Jan Beulich

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=5315B760.3080408@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --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.