From: Dave Jones <davej@redhat.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Adrian Bunk <bunk@stusta.de>, Andrew Morton <akpm@osdl.org>,
David Howells <dhowells@redhat.com>,
Neil Brown <neilb@cse.unsw.edu.au>,
"bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>,
linux-kernel@vger.kernel.org, alex@hausnet.ru, mingo@redhat.com,
ak@suse.de
Subject: Re: [Bugme-new] [Bug 7495] New: Kernel periodically hangs.
Date: Sun, 12 Nov 2006 16:45:40 -0500 [thread overview]
Message-ID: <20061112214540.GB31649@redhat.com> (raw)
In-Reply-To: <1163340998.3293.131.camel@laptopd505.fenrus.org>
On Sun, Nov 12, 2006 at 03:16:38PM +0100, Arjan van de Ven wrote:
>
> > > We KNOW it can't work on a sizable amount of machines. This is why it
> > > is a config option; you can enable it if YOUR machine is KNOWN to work,
> > > and you get some gains. But it's also understood that it often it won't
> > > work. So any sensible distro (since they have to aim for a wide
> > > audience) disables this option ...
> >
> > Nowadays, many distributions only ship CONFIG_SMP=y kernels...
>
> that's a calculated risk on their side (and they know that); they're
> balancing not functioning on a set of machines off against needing more
> kernels.
Andi has a nice patch in the suse kernel which adds heuristics to disable
apic on systems where it isn't likely to work. It DTRT in at least
one problem case that I know of. The actual fall-out from enabling
'run SMP kernels on UP i686' for FC6 has mostly been a non-event.
Literally a handful of cases, that will likely all get caught and worked
around by Andi's patch or similar.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-11-12 21:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200611111129.kABBTWgp014081@fire-2.osdl.org>
2006-11-11 18:00 ` [Bugme-new] [Bug 7495] New: Kernel periodically hangs Andrew Morton
2006-11-11 18:10 ` Arjan van de Ven
2006-11-11 18:19 ` Andrew Morton
2006-11-12 11:50 ` Arjan van de Ven
2006-11-12 12:53 ` Adrian Bunk
2006-11-12 13:16 ` Arjan van de Ven
2006-11-12 13:37 ` Adrian Bunk
2006-11-12 13:57 ` Arjan van de Ven
2006-11-12 14:10 ` Adrian Bunk
2006-11-12 14:16 ` Arjan van de Ven
2006-11-12 15:21 ` Adrian Bunk
2006-11-12 15:50 ` Arjan van de Ven
2006-11-12 15:59 ` Patrick McFarland
2006-11-12 16:07 ` Arjan van de Ven
2006-11-12 16:47 ` Adrian Bunk
2006-11-12 21:45 ` Dave Jones [this message]
2006-11-13 2:07 ` Andi Kleen
2006-11-12 19:18 ` Ingo Oeser
2006-11-12 19:34 ` Andrew Morton
2006-11-12 20:32 ` Arjan van de Ven
2006-11-13 6:42 ` Neil Brown
2006-11-13 11:22 ` David Howells
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=20061112214540.GB31649@redhat.com \
--to=davej@redhat.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=alex@hausnet.ru \
--cc=arjan@infradead.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bunk@stusta.de \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=neilb@cse.unsw.edu.au \
/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.