Catch up on stories from the past week (and beyond) at the Slashdot story archive

 


Forgot your password?
Close
typodupeerror
×
BSD Operating Systems

NetBSD-Current Gets SMP 41

Posted by timothy from the build-a-bigger-box dept.
MobyTurbo writes "NetBSD-current for the i386 architecture now has SMP. (It used to be that only FreeBSD had this feature among the free BSDs.) See the announcement on the current-users mailing list."
This discussion has been archived. No new comments can be posted.

NetBSD-Current Gets SMP More

NetBSD-Current Gets SMP

Comments Filter:
  • When will the Dreamcast Port [netbsd.org] get it?

    I really want to try this out on my quad-proc Dreamcast.

    </sarcasm>
    • Nah, if only they'd get it working on the sparc port, then I'd have a reason to go out and find another SM51 processor for my SS10...
  • Finally OpenBSD will ahve some straight up competition. For a long time it has been the most secure, and the only BSD with SMP support. Now we will finally see the battle for BSD supremacy heating up!

    Can't wait to see what FreeBSD does to top this!
    • According the the summary at the top, it's FreeBSD that has it and OpenBSD doesn't.
    • Blockquoth the poster:
      Finally OpenBSD will ahve some straight up competition. For a long time it has been the most secure, and the only BSD with SMP support.

      Can't wait to see what FreeBSD does to top this!

      According to the official OpenBSD FAQ [openbsd.org], OpenBSD does not have SMP [openbsd.org]. Either in -CURRENT (development branch) or in release form, though apparantly there is a group working on it. FreeBSD on the other hand will [freebsd.org] have an improved fine-grain implementation of SMP, in their upcoming 5.0 release, and already have a more primative version in the 4.x releases. It's really the reverse, OpenBSD is the only free *BSD *without* SMP being tested. I have no idea why you thought otherwise.
    • OpenBSD has never had SMP, and if you read any of the OpenBSD mailing lists, you will see that it is not a priority to have SMP. And there is no battle for BSD supremacy; the BSDs peacefully coexist, each standing on its own merits.

  • yawn (Score:4, Insightful)

    by honold ( 152273 ) on Thursday October 03, 2002 @04:21PM (#4383181)
    call me crazy, but i could really care less about smp. i would wager the wide majority of smp systems fall into 2 categories:

    1) unnecessarily powerful servers
    2) unnecessarily powerful home braggart systems

    database servers? sure. heavily loaded web servers? sure. file servers? NO. desktops? NO.

    at least the scsi bigots will actually net some measurable performance increases if they drop some money on a 15k drive.

    i sincerely hope openbsd continues to focus on OTHER things like openssh - you know, that thing you probably use every day of your life on your non-smp machine?. since most openbsd boxes are used as edge devices, the only big need for processing horespower is in crypto...

    and that problem can be solved by purchasing a hifn-based pci crypto accellerator for $90 from soekris.com, thanks to openbsd's excellent hardware crypto accelerator support.

    once you get past the crotch-grabbing aspect, low-end smp is not what most of the world would have you believe it is. high-end smp will likely get replaced by clustering of commodity hardware.

    • Re:yawn (Score:3, Interesting)

      by OrangeSpyderMan ( 589635 )
      call me crazy

      Ok, crazy guy. :-)

      I'll bite. I am currently running two SMP machines. Ok, one is for a DB server. Leave that one out of the question, it is actually underpowered for much of what it does, alas. I'm saving my pennies. The other however is my main desktop. It is not unecessarily powerful (2xPIII 600EB) compared to todays desktops systems, on the contrary, but I would never swap it for a single 1.2GHz (or even higher - a 2.8 P4 might get me thinking :-) ).

      The reason is simple. On my desktop I frequently have a number of concurrent processes running (Mozilla, compile, ogg player, a few ssh sessions and I might even fire up a game from time to time while I'm waiting for a compile to finish...). This kind of use shows what a boost "low-end" SMP can be - the system remains perfectly responsive way past loads that would have a similar "horse-power" single CPU system groaning - and that is very important for interactive desktop use. My box at the office is a single PIII 1 GHz, which should, on paper, hold its own quite well. It feels markedly more sluggish for desktop use.

      SMP systems are little more prone to "pissing competition" type purchases than say, GeForces and P4. I don't know many people who can actually use all the horsepower of modern systems on the desktop, be it under *BSD or Linux. As someone once said, todays desktops just "wait faster". At the moment at least I'd take a lesser CPU 2-way SMP system over a more powerful single CPU for my desktop anyday.
      • you still have io, memory, and chipset performance to improve or bog down your results

        that aside, i'd love to see a single metric (really, just one) where a 1.2ghz p3 would get outperformed by 2 underclocked tualatin p3s (to make the competition fair - they'd blow the 600ebs away) on the exact same rig.

        2x600mhz != 1.2ghz. it's more around 900mhz average, if you're lucky.
    • While I agree that most home systems don't have much use for an SMP system, you are making an overly broad generalization. When you say "desktops", you're including a whole lot of computers and their users, many of whom do more with their systems than browse the web and play games. Compiling software is one task that my computers regularly perform, for both work and personal projects, and let me tell you, SMP can greatly reduce the number of hours per week I spend waiting for my computer to finish. Video encoding is another task that some of my friends do at both home and work, and it greatly benefits from a second CPU. I'm sure there are other such tasks that, while not mainstream activities that mom and dad would be doing in the living room, are certainly common.

  • Port to OpenBSD soon perhaps? (Score:3, Interesting)

    by moonboy ( 2512 ) on Thursday October 03, 2002 @04:25PM (#4383212)


    I wonder if this means OpenBSD will soon have SMP capability? Anyone have any thoughts? Inside information?

  • netbsd and smp (Score:4, Informative)

    by rplacd ( 123904 ) on Thursday October 03, 2002 @04:31PM (#4383273) Homepage
    Note that while the i386 port just got SMP support, other ports have had it for a while. NetBSD/macppc got it in August, NetBSD/sparc got it over a year ago, etc.

  • Wow! (Score:2, Funny)

    by Dimwit ( 36756 )
    Now BSD can die twice as fast!

    (Note to moderators: Not a troll - just an sad attempt at humour. I'm writing this from my FreeBSD 4.6.2-RELEASE box...)

  • At work I have a dual processor 'Windtunnel' Apple Mac running Mac OS X. Does this not count as SMP? Or have I misunderstood the term?

    (Dawin is of course a flavour of BSD)
    • Hmm well sort of.. it actually is build on the mach kernel which was a fork of bsd way back when.

      Of course this is NET-BSD not BSD. FreeBSD I believe has had SMP support for a while now. FreeBSD is more like Darwin / Mac OS X than NetBSD. Also they are referring to the i386 which is way different from Mac which uses the motorola processor.

      NetBSD runs on just about all processors out there, does Mac OS X? No and neither does FreeBSD. That is what the whole NetBSD project is about. Mac OS X is about a pretty gui on the foundations of UNIX / BSD. Kinda about time someone did what Mac did, but then again about a year before Apple announced their plans of OS X I suggested that someone put a nice GUI on UNIX. Guess what. They listened and now everyone is really taking to Mac.

    • When people on slashdot speak of BSD, they tend to mean the post 386BSD derivatives. That was the "Free" OS that sprung NetBSD and FreeBSD. Then OpenBSD branched from NetBSD. Until fairly recently, none of these were SMP capable. For a while, only FreeBSD was SMP capable, now it looks like the "Free" BSDs (386BSD derived) are all rounding out, and starting to overlap in scope. FreeBSD now runs on non x86 hardware, and NetBSD now runs SMP. OpenBSD has various groups bringing SMP (mostly from NetBSD work) and NetBSD/FreeBSD are reincorporating OpenBSD code-audit correction. On the whole, it is a very pleasing situation.

      Now MacOS, which runs on top of Darwin, has a slightly different heritage. It comes from BSD, but I believe it derives from a pre-386BSD branch (although they have incorporated many imporvements from NetBSD, then FreeBSD). It probably it pretty directly decended from LITES, a BSD "personality" which ran ontop of the MACH microkernel. That doesn't necessarily mean that LITES or Darwin is a Microkernel system - rather, they are a "single server" - a single kernel hosted ontop of the MACH subsystems. This means it takes advantage of MACH VM architecture, and probably MACH hardware drivers, but it doesn't take advantage of MACH message passing or other mk technologies.

      Much like Windows NT was designed as a microkernel, they ended up defeating the micrkernel architecture to preserve system performance, without wasting previous effort. In this case, the previous effort was from NeXTSTEP, which also ran ontop of MACH. Then Apple incorporated updates to MACH (2.5 to 3.0) IIRC, BSD (4.3 to 4.4) and OpenStep... and every other technology that came since.

      There is much more info to google for, but I believe I have thorougly answered your question. Just remember, there is traditional BSD (usually referring to BSD4.4, as opposed to AT&T SYSV) and there is Post-UCB unencumbered BSD (usually 386BSD derived legally unencumbered forks under a "BSD" style Free Software license).
  • See subject line. AFAICR, x86 "SMP" under NetBSD was only spinup, it could 'see' more cpu's, and spin them up, but it never did anything with the extra cpus. Do they finally have stuff like threading and running processes on more cpus in order? I don't own SMP boxes, but there's a couple of places where I worked that would drool over a stable SMP NetBSD box if that was possible :)

    Hmm... Time to scour off the netbsd-current@ mailinglists again for answers...

Slashdot Top Deals

It is easier to write an incorrect program than understand a correct one.

Close