All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Collins <bcollins@ubuntu.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: SMP on UP (Was Re: State of the Linux PCI and PCI Hotplug	Subsystems for	2.6.16-rc5)
Date: Thu, 09 Mar 2006 16:06:47 -0500	[thread overview]
Message-ID: <1141938407.4406.4.camel@grayson> (raw)
In-Reply-To: <1141937556.13319.64.camel@mindpipe>

On Thu, 2006-03-09 at 15:52 -0500, Lee Revell wrote:
> On Thu, 2006-03-09 at 15:10 -0500, Ben Collins wrote:
> > The difference between our 2.6.15 386 and 686 kernels is actually pretty
> > huge. The 386 is M486, and UP, while our 686 kernel is M686, and SMP.
> > The SMP is also complicated by our use of the SMP-alternatives patch,
> > but I believe I had this user test with this disabled (kernel command
> > line option that leaves all the SMP code intact for testing). It didn't
> > alter the problem. 
> 
> Ubuntu doesn't provide a UP 686 kernel?
> 
> Isn't there a performance hit running an SMP kernel on UP?

This is a little off-topic to the original thread, so trimming CC and
changing subject.

As mentioned above, we have the SMP-alternatives patch, which will
basically convert SMP related code (lock op's and some atomic
operations) to UP, on-the-fly (at boot for the kernel, and at load for
modules). It's not 100% the same as running a UP kernel, but it comes
close enough that it allows us to distribute fewer kernels. This equates
to less load on us and our users.

I don't want to start this whole thread over again, so check back in the
linux-kernel archives for the SMP alternatives patch thread.

-- 
Ubuntu     - http://www.ubuntu.com/
Debian     - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
SwissDisk  - http://www.swissdisk.com/


  reply	other threads:[~2006-03-09 21:07 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-06 22:35 State of the Linux PCI and PCI Hotplug Subsystems for 2.6.16-rc5 Greg KH
2006-03-06 22:47 ` Sam Ravnborg
2006-03-06 23:00   ` Greg KH
2006-03-08 22:26 ` Adrian Bunk
2006-03-08 22:50   ` Greg KH
2006-03-08 23:03     ` Linus Torvalds
2006-03-08 23:18       ` Greg KH
2006-03-08 23:30         ` Linus Torvalds
2006-03-09 18:40           ` Tomasz Torcz
2006-03-09 19:49             ` Linus Torvalds
2006-03-09 20:10               ` Ben Collins
2006-03-09 20:24                 ` Linus Torvalds
2006-03-15 16:03                   ` Ben Collins
2006-03-09 20:52                 ` Lee Revell
2006-03-09 21:06                   ` Ben Collins [this message]
2006-03-09 21:47                     ` SMP on UP (Was Re: State of the Linux PCI and PCI Hotplug Subsystems for 2.6.16-rc5) Lee Revell
2006-03-09 21:07                   ` State of the Linux PCI and PCI Hotplug Subsystems for 2.6.16-rc5 David S. Miller
2006-03-09 20:37               ` Arjan van de Ven
2006-03-09 20:46                 ` Dave Jones
2006-03-09 21:15                   ` Arjan van de Ven
2006-03-08 23:29       ` Andrew Morton
2006-03-08 23:45         ` Dave Hansen
2006-03-08 23:52           ` Andrew Morton
2006-03-09 10:24         ` Martin MOKREJŠ
2006-03-08 23:05     ` Adrian Bunk
2006-03-08 23:18       ` Lee Revell
2006-03-08 23:23         ` Greg KH
2006-03-08 23:34           ` Lee Revell
2006-03-08 23:40             ` Greg KH
2006-03-09  0:03               ` Lee Revell
2006-03-08 23:21       ` Greg KH
2006-03-09  4:01 ` Kenji Kaneshige
2006-03-09  5:34   ` Greg KH
2006-03-09  5:11 ` Lee Revell

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=1141938407.4406.4.camel@grayson \
    --to=bcollins@ubuntu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.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 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.