From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Avi Kivity <avi@redhat.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Xen-devel <xen-devel@lists.xensource.com>,
Jan Beulich <jbeulich@novell.com>, Ingo Molnar <mingo@elte.hu>,
Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: Question about x86/mm/gup.c's use of disabled interrupts
Date: Thu, 19 Mar 2009 10:16:57 -0700 [thread overview]
Message-ID: <49C27E09.5070307@goop.org> (raw)
In-Reply-To: <49C21473.2000702@redhat.com>
Avi Kivity wrote:
>> And the hypercall could result in no Xen-level IPIs at all, so it
>> could be very quick by comparison to an IPI-based Linux
>> implementation, in which case the flag polling would be particularly
>> harsh.
>
> Maybe we could bring these optimizations into Linux as well. The only
> thing Xen knows that Linux doesn't is if a vcpu is not scheduled; all
> other information is shared.
I don't think there's a guarantee that just because a vcpu isn't running
now, it won't need a tlb flush. If a pcpu does runs vcpu 1 -> idle ->
vcpu 1, then there's no need for it to do a tlb flush, but the hypercall
can make force a flush when it reschedules vcpu 1 (if the tlb hasn't
already been flushed by some other means).
(I'm not sure to what extent Xen implements this now, but I wouldn't
want to over-constrain it.)
>> Also, the straightforward implementation of "poll until all target
>> cpu's flags are clear" may never make progress, so you'd have to
>> "scan flags, remove busy cpus from set, repeat until all cpus done".
>>
>> All annoying because this race is pretty unlikely, and it seems a
>> shame to slow down all tlb flushes to deal with it. Some kind of
>> global "doing gup_fast" counter would get flush_tlb_others bypass the
>> check, at the cost of putting a couple of atomic ops around the
>> outside of gup_fast.
>
> The nice thing about local_irq_disable() is that it scales so well.
Right. But it effectively puts the burden on the tlb-flusher to check
the state (implicitly, by trying to send an interrupt). Putting an
explicit poll in gets the same effect, but its pure overhead just to
deal with the gup race.
I'll put a patch together and see how it looks.
J
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-03-19 17:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 19:17 Jeremy Fitzhardinge
2009-03-18 21:13 ` Avi Kivity
2009-03-18 21:23 ` Jeremy Fitzhardinge
2009-03-18 21:40 ` Avi Kivity
2009-03-18 22:14 ` Jeremy Fitzhardinge
2009-03-18 22:41 ` Avi Kivity
2009-03-18 22:55 ` Jeremy Fitzhardinge
2009-03-18 23:05 ` Avi Kivity
2009-03-18 23:32 ` Jeremy Fitzhardinge
2009-03-19 9:46 ` Avi Kivity
2009-03-19 17:16 ` Jeremy Fitzhardinge [this message]
2009-03-19 17:33 ` Avi Kivity
[not found] ` <70513aa50903181617r418ec23s744544dccfd812e8@mail.gmail.com>
2009-03-18 23:37 ` Jeremy Fitzhardinge
2009-03-19 1:32 ` Nick Piggin
2009-03-19 17:31 ` Jeremy Fitzhardinge
2009-03-20 4:40 ` Paul E. McKenney
2009-03-20 15:38 ` Jeremy Fitzhardinge
2009-03-20 15:57 ` Paul E. McKenney
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=49C27E09.5070307@goop.org \
--to=jeremy@goop.org \
--cc=avi@redhat.com \
--cc=jbeulich@novell.com \
--cc=keir.fraser@eu.citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox