From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
Cliff Wickman <cpw@sgi.com>, Jack Steiner <steiner@sgi.com>
Subject: Re: [GIT PULL] x86/uv changes for v3.6
Date: Sun, 22 Jul 2012 21:11:20 +0200 [thread overview]
Message-ID: <20120722191120.GA10328@gmail.com> (raw)
In-Reply-To: <CA+55aFyh9+ZGjP+3kP1_bqmSVLxsHvWP967ZnEFHuda1MhAZ8w@mail.gmail.com>
* Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Sun, Jul 22, 2012 at 7:15 AM, Ingo Molnar <mingo@kernel.org> wrote:
> >
> > UV2 BAU productization fixes.
>
> These kinds of "explanations" are not helpful, Ingo. Nobody
> except the SGI people know what the hell those TLA's mean. So
> please don't use random TLA's to "explain" things.
Sorry!
The Broadcast Assist Unit is SGI's fancy out of line way on UV
hardware to do TLB flushes, instead of the normal APIC IPI
methods. The commits here fix / work around hangs in their
latest hardware iteration (UV2).
My understanding is that the main purpose of the out of line
signalling channel is to improve scalability: the UV APIC
hardware glue does not handle broadcasting to many CPUs very
well, and this matters most for TLB shootdowns.
[ I don't agree with all aspects of the current approach: in
hindsight it would have been better to link the BAU at the
IPI/APIC driver level instead of the TLB shootdown level,
where TLB flushes are really just one of the uses of broadcast
SMP messages. Doing that would improve scalability in some
other ways and it would also remove a few uglies from the TLB
path. It would also be nice to push more is_uv_system() tests
into proper x86_init or x86_platform callbacks. Cliff? ]
Thanks,
Ingo
prev parent reply other threads:[~2012-07-22 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-22 14:15 [GIT PULL] x86/uv changes for v3.6 Ingo Molnar
2012-07-22 17:36 ` Linus Torvalds
2012-07-22 19:11 ` Ingo Molnar [this message]
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=20120722191120.GA10328@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cpw@sgi.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox