From: "Jan Beulich" <jbeulich@novell.com>
To: "Jeremy Fitzhardinge" <jeremy@goop.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Chris Lalancette" <clalance@redhat.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH]: Fix Xen domU boot with batched mprotect
Date: Thu, 16 Oct 2008 08:28:33 +0100 [thread overview]
Message-ID: <48F70941.76E4.0078.0@novell.com> (raw)
In-Reply-To: <48F61919.2050005@goop.org>
>>> Jeremy Fitzhardinge <jeremy@goop.org> 15.10.08 18:23 >>>
>> But
>> performance-wise, CONFIG_HIGHPTE sucks under Xen anyway, so you'd
>> better not turn this on in the first place. We may want/need to provide
>> a means to disable this at run time so the same kernel when run natively
>> could still make use of it, but without impacting performance under Xen.
>>
>
>That's a secondary issue. What's the source of the performance hit?
>Just all the extra kmap_atomic operations?
Yes, afaict.
WARNING: multiple messages have this Message-ID (diff)
From: "Jan Beulich" <jbeulich@novell.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Chris Lalancette <clalance@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: Fix Xen domU boot with batched mprotect
Date: Thu, 16 Oct 2008 08:28:33 +0100 [thread overview]
Message-ID: <48F70941.76E4.0078.0@novell.com> (raw)
In-Reply-To: <48F61919.2050005@goop.org>
>>> Jeremy Fitzhardinge <jeremy@goop.org> 15.10.08 18:23 >>>
>> But
>> performance-wise, CONFIG_HIGHPTE sucks under Xen anyway, so you'd
>> better not turn this on in the first place. We may want/need to provide
>> a means to disable this at run time so the same kernel when run natively
>> could still make use of it, but without impacting performance under Xen.
>>
>
>That's a secondary issue. What's the source of the performance hit?
>Just all the extra kmap_atomic operations?
Yes, afaict.
next prev parent reply other threads:[~2008-10-16 7:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 11:03 [PATCH]: Fix Xen domU boot with batched mprotect Chris Lalancette
2008-10-15 11:03 ` Chris Lalancette
2008-10-15 15:24 ` [Xen-devel] " Jan Beulich
2008-10-15 15:24 ` Jan Beulich
2008-10-15 16:23 ` Jeremy Fitzhardinge
2008-10-15 16:23 ` Jeremy Fitzhardinge
2008-10-16 7:28 ` Jan Beulich [this message]
2008-10-16 7:28 ` Jan Beulich
2008-10-16 9:58 ` [Xen-devel] " Jan Beulich
2008-10-16 9:58 ` Jan Beulich
2008-10-16 16:10 ` Jeremy Fitzhardinge
2008-10-16 16:10 ` Jeremy Fitzhardinge
2008-10-17 7:12 ` [Xen-devel] " Jan Beulich
2008-10-17 7:12 ` Jan Beulich
2008-10-17 15:19 ` Jeremy Fitzhardinge
2008-10-17 15:19 ` Jeremy Fitzhardinge
2008-10-17 15:30 ` [Xen-devel] " Jan Beulich
2008-10-17 15:30 ` Jan Beulich
2008-10-17 15:36 ` [Xen-devel] " Jeremy Fitzhardinge
2008-10-17 15:36 ` Jeremy Fitzhardinge
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=48F70941.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=clalance@redhat.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--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.