From: Benjamin LaHaise <bcrl@kvack.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Andi Kleen <ak@muc.de>, Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, virtualization@lists.osdl.org,
xen-devel@lists.xensource.com, Chris Wright <chrisw@sous-sol.org>,
Zachary Amsden <zach@vmware.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Ingo Molnar <mingo@redhat.com>, Andi Kleen <ak@suse.de>
Subject: Re: [patch 28/34] Xen-pv_ops: Xen SMP guest support
Date: Wed, 14 Mar 2007 09:28:20 -0400 [thread overview]
Message-ID: <20070314132820.GL6209@kvack.org> (raw)
In-Reply-To: <20070313233034.586018620@goop.org>
On Tue, Mar 13, 2007 at 04:30:45PM -0700, Jeremy Fitzhardinge wrote:
> [ brcl, mingo: Would you mind having a close look at the code in
> xen_exit_mm and drop_mm_ref? - Thanks ]
I see what you're doing here, and this comment seems to allude to the reasons
behind it without spelling it out.
> +/*
> + * We aggressively remove defunct pgd from cr3. We execute unmap_vmas()
> + * *much* faster this way.
> + */
Are you switching mms in order to avoid all of the overhead associated with
flushing an active mm during task exit? If so, it makes much more sense to
do this in the generic helper, as it should be a win on x86 and x86-64
where switching to init_mm is relatively low cost given the support for
global pages. I'll run some tests on a couple of systems this evening and
post the results.
-ben
--
"Time is of no importance, Mr. President, only life is important."
Don't Email: <zyntrop@kvack.org>.
next parent reply other threads:[~2007-03-14 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070313233017.933601256@goop.org>
[not found] ` <20070313233034.586018620@goop.org>
2007-03-14 13:28 ` Benjamin LaHaise [this message]
2007-03-14 15:05 ` [patch 28/34] Xen-pv_ops: Xen SMP guest support Jeremy Fitzhardinge
2007-03-14 20:23 ` Zachary Amsden
[not found] ` <20070313233031.149028836@goop.org>
2007-03-16 2:38 ` [patch 10/34] Xen-pv_ops: Simplify smp_call_function*() by using common implementation Randy Dunlap
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=20070314132820.GL6209@kvack.org \
--to=bcrl@kvack.org \
--cc=ak@muc.de \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=chrisw@sous-sol.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.com \
--cc=zach@vmware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox