From: Pavel Machek <pavel@suse.cz>
To: Mike Travis <travis@sgi.com>
Cc: Nick Piggin <npiggin@suse.de>, Jack Steiner <steiner@sgi.com>,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
linux-kernel@vger.kernel.org, Cliff Wickman <cpw@sgi.com>,
Russ Anderson <rja@sgi.com>
Subject: Re: [patch] x86: make UV support optional
Date: Sun, 11 Jan 2009 19:39:36 +0100 [thread overview]
Message-ID: <20090111183935.GC2217@ucw.cz> (raw)
In-Reply-To: <49637346.6060105@sgi.com>
Hi!
> The problem arises that if the option becomes too obscure (and never
> enabled), then it won't get tested. We (as many companies do) rely on
> distros to certify applications and security features using a standard
> kernel, and if an option (such as X86_UV) causes any problems whatsoever,
> they'll drop it and we no longer have that application certification.
If SGI UV is really important, I'm sure you can ask distros to keep it
enabled.
> Currently, Ingo's test setup sets MAXSMP quite a bit and he's found
> many problems with large NR_CPUS counts that we never would have found
> ourselves. Please don't make that process any harder.
Yeah, and remove config_386 too. Just hardcode it to y.
No, sorry, I don't see why we should treat UV specially.
> In fact, 13k is peanuts. Why don't you set something like "very minimal
13K is quite a lot, actually.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-01-11 19:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 6:03 [patch] x86: make UV support optional Nick Piggin
2009-01-06 6:38 ` Yinghai Lu
2009-01-06 6:44 ` Nick Piggin
2009-01-06 9:01 ` Ingo Molnar
2009-01-06 12:23 ` Nick Piggin
2009-01-06 12:31 ` Ingo Molnar
2009-01-06 14:33 ` Jack Steiner
2009-01-06 14:48 ` Nick Piggin
2009-01-06 15:05 ` Mike Travis
2009-01-06 15:30 ` Nick Piggin
2009-01-11 18:39 ` Pavel Machek [this message]
2009-01-06 14:54 ` Mike Travis
2009-01-06 15:04 ` Nick Piggin
2009-01-06 15:28 ` Ingo Molnar
2009-01-06 15:31 ` Mike Travis
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=20090111183935.GC2217@ucw.cz \
--to=pavel@suse.cz \
--cc=cpw@sgi.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=npiggin@suse.de \
--cc=rja@sgi.com \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.de \
--cc=travis@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