From: Cliff Wickman <cpw@sgi.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
steiner@sgi.com, mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: Comments on UV tlb flushing
Date: Tue, 29 Jul 2008 15:04:55 -0500 [thread overview]
Message-ID: <20080729200455.GA20559@sgi.com> (raw)
In-Reply-To: <488F5781.2030909@goop.org>
On Tue, Jul 29, 2008 at 10:46:41AM -0700, Jeremy Fitzhardinge wrote:
> Cliff Wickman wrote:
>> But if the tlb_uv.o code should be present in "every" distro x86 kernel
>> I don't see the point of having to configure it in. Why not just
>> configure it out for small (embedded) kernels?
>
> Because it's not an binary thing. Lots of people who are compiling
> their own kernels for specialized uses don't set CONFIG_EMBEDDED, but
> also don't want a kitchen sink kernel. 6k isn't that much, but if every
> obscure platform enabled some always-on code it rapidly starts to build
> up.
But UV will not be obscure! It will be common among x86_64 :)
I know what you're talking about. It may sometimes be useful to turn
off chunks of code you don't need.
But is the specialized application of 64-bit processors big enough to
warrant the feature?
The size of most any 64-bit system would, I would think, make 6k of
code insignificant.
And the more options you add, the more likely someone will pick
combinations that won't work together.
> Basically, if you want to make sure if you're going to get some level of
> distro support, you need to make contact with the distros directly and
> talk about what you'd like them to do.
> J
And we do. And could reasonably expect that they would turn on that
option for x86_64 kernels. We'd just, of course, rather not have to watch
and prompt to be sure all x86_64 kernels will run on our hardware.
-Cliff
--
Cliff Wickman
Silicon Graphics, Inc.
cpw@sgi.com
(651) 683-3824
next prev parent reply other threads:[~2008-07-29 20:05 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
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 [this message]
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=20080729200455.GA20559@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).