From: Cliff Wickman <cpw@sgi.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>, jeremy@goop.org
Cc: steiner@sgi.com, mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: Comments on UV tlb flushing
Date: Tue, 29 Jul 2008 08:32:04 -0500 [thread overview]
Message-ID: <20080729133204.GA13138@sgi.com> (raw)
In-Reply-To: <200807291412.18495.nickpiggin@yahoo.com.au>
On Tue, Jul 29, 2008 at 02:12:18PM +1000, Nick Piggin wrote:
> On Tuesday 29 July 2008 10:28, Jeremy Fitzhardinge wrote:
> > I'm just reworking the x86 tlb code to use smp_call_function_mask, and I
> > see how the UV tlb flushing hooks in. A few things occur to me:
> >
> > 1. There should be a CONFIG_X86_UV to select this code. tlb_uv.o is
> > around 6k, which is not trivial overhead to subject every x86_64
> > kernel to.
>
> Definitely.
I'd like to talk about this issue separate from the virtualization one.
I think that the Linux distributions are not going to build a special
UV kernel, are they? So every distro would have to be prompted to
turn on CONFIG_X86_UV, or else their kernel is not going to boot on UV.
But you have a point about not linking the 6k UV object file where
size is an issue.
Thanks for catching that.
Perhaps the UV code should be excluded if CONFIG_EMBEDDED is set.
-Cliff
next prev parent reply other threads:[~2008-07-29 13:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 0:28 Comments on UV tlb flushing Jeremy Fitzhardinge
2008-07-29 4:12 ` Nick Piggin
2008-07-29 6:26 ` Jeremy Fitzhardinge
2008-07-29 13:32 ` Cliff Wickman [this message]
2008-07-29 14:43 ` Jeremy Fitzhardinge
2008-07-29 17:34 ` Cliff Wickman
2008-07-29 17:46 ` Jeremy Fitzhardinge
2008-07-29 20:04 ` Cliff Wickman
2008-07-29 18:13 ` Yinghai Lu
2008-07-29 18:25 ` Jeremy Fitzhardinge
2008-07-29 18:45 ` Mike Travis
2008-07-29 19:12 ` 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=20080729133204.GA13138@sgi.com \
--to=cpw@sgi.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=steiner@sgi.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.