From: Giuliano Pochini <pochini@shiny.it>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>,
Lee Braiden <lee_b@member.fsf.org>
Subject: Re: SMP kernels on single processor machines
Date: Fri, 21 May 2004 12:34:44 +0200 (CEST) [thread overview]
Message-ID: <XFMail.20040521123444.pochini@shiny.it> (raw)
In-Reply-To: <1085097417.9801.5.camel@gaston>
On 20-May-2004 Benjamin Herrenschmidt wrote:
>
> On Thu, 2004-05-20 at 21:48, Lee Braiden wrote:
>
>> But I quit doing that at some point, after someone (authoritative, but I
>> can't remember the details) pointed out that it added complexity,
>> debugging issues, etc. Given that I *already* have problems with PPC
>> kernels -- latency/lockups, (preempting?), alsa sound, video res, etc.,
>> I personally wouldn't go near this until I'm fairly confident that the
>> other stuff is solid in its own right.
>>
>> But then, I'm just a luser, not a kernel maintainer ;D
>
> Yah, well... CONFIG_PREEMPT gives you all the problems of SMP without
> any benefit so .... :)
2.6.6 has the CONFIG_PREEMPT option so I thought it was stable.
Isn't it ? What are the known problem ? Is only preempt+smp
known to have problems ?
--
Giuliano.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-05-21 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 10:58 SMP kernels on single processor machines Jens Schmalzing
2004-05-20 11:48 ` Lee Braiden
2004-05-20 23:56 ` Benjamin Herrenschmidt
2004-05-21 10:34 ` Giuliano Pochini [this message]
2004-05-21 11:11 ` Benjamin Herrenschmidt
2004-05-21 12:30 ` Lee Braiden
2004-05-21 12:58 ` Marius Groeger
2004-05-21 23:11 ` Benjamin Herrenschmidt
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=XFMail.20040521123444.pochini@shiny.it \
--to=pochini@shiny.it \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).