linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Lee Braiden <lee_b@member.fsf.org>
To: linuxppc-dev@lists.linuxppc.org, debian-powerpc@lists.debian.org
Subject: Re: SMP kernels on single processor machines
Date: Thu, 20 May 2004 12:48:24 +0100	[thread overview]
Message-ID: <40AC9B08.7010602@member.fsf.org> (raw)
In-Reply-To: <hhad03tlet.fsf@alsvidh.mathematik.uni-muenchen.de>


Jens Schmalzing wrote:

>SMP kernels run
>fine on single processor machines.  I have repeatedly been told,
>however, that this bears a considerable performance hit on some
>hardware.  Can anybody confirm or deny this?  Even small hints would
>be appreciated.
>
>
A long time ago, I used to compile SMP into my kernels just on the
coolness factor, and on the promise that 'one day, soon, I'll get me a
decent machine' :)

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

--
Lee Braiden
lee_b@member.fsf.org


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-05-20 11:48 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 [this message]
2004-05-20 23:56   ` Benjamin Herrenschmidt
2004-05-21 10:34     ` Giuliano Pochini
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=40AC9B08.7010602@member.fsf.org \
    --to=lee_b@member.fsf.org \
    --cc=debian-powerpc@lists.debian.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).