9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: jmk@plan9.bell-labs.com jmk@plan9.bell-labs.com
Subject: porting linux programs and drivers to plan9
Date: Fri, 18 Apr 1997 00:59:04 -0400	[thread overview]
Message-ID: <19970418045904.KM5cV9fXFb_s7BKsyKoAEhKWEJSmo2Ip4cP2iQpUh2E@z> (raw)

	> Also of real interest is the MPSpec work being done in the Linux
	>and FreeBSD camps.  I have a dual PPRO-150 (Tyan S1668) box I hope 
	>to get Plan9 to work in a multiprocessor mode... that'd be fun.  
	>The PPRO 150s are already pretty fast (compared to the P133s I
	>was using :) ) but having dual PPROs would really rock.  Dual PPRO
	>200s would REALLY scream (evil grin).
	>
	>Q: Are Brazil (which apparently supports some Pentium multiprocessor 
	>boards) and Plan9 sufficiently similar that the Brazil MP stuff would 
	>be of use?  Is is possible to obtain some of the Brazil MP stuff?

Last October I wrote in 9fans:

	The x86 multiprocessor code runs on Pentium or Pentium Pro systems which
	conform to the Intel Multiprocessor Specification, there were no changes
	required for the Pentium Pro. There's about 1000 lines of code, most of it
	is concerned with parsing the configuration table created by the BIOS. A
	small number of changes were made to the base x86 code - some mmu data
	structures were made per-processor and some locks were added to some device
	drivers where uniprocessor operation had been assumed. The only change
	in the port code was changing 6 references of 'm->' to 'MACHP(m->machno)->'
	in proc.c as the nature of the x86 mmu required 'm' to be a fixed virtual
	address.

Since then we've found one problem caused by the weak memory ordering of the Pentium
Pro, there may be others lurking, time will tell. I can't think offhand of any reason
the same changes couldn't be made to Plan9. It took about two weeks total to have
full SMP implemented on the x86, Plan9 is 'SMP-friendly' and was designed with this
is mind. Compare this to Linux where, after 2 years, the first tentative steps at
allowing multiple processors to run kernel code simultaneously are just being made.

And yes, dual Pentium Pros make a respectably fast system:

	a% echo $sysname
	anna
	a% cd /sys/src/brazil/pc
	a% mk clean
	rm -f *.[v486x] *.root.s cfs.h fs.h init.h conf.h *.out
	for(i in pc pccpu pcdinar pcdisk)
		rm -f $i.c [9bz]$i boot$i.*
	a% time mk 'CONF=pccpu'>/dev/null
	12.27u 9.93s 23.81r 	 mk CONF=pccpu
	a% 

Anna is a dual 200MHz Pentium Pro (ASUS P6NP5 motherboard with 256MB EDO)
connected to the fileserver via 100Base-TX.

--jim




             reply	other threads:[~1997-04-18  4:59 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-04-18  4:59 jmk [this message]
  -- strict thread matches above, loose matches on Subject: below --
1997-04-21 20:59 miller
1997-04-21 16:27 Eric
1997-04-21 14:53 Milon
1997-04-21 12:50 miller
1997-04-21 11:29 Nigel
1997-04-21  8:05 Boyd
1997-04-21  7:16 chad
1997-04-21  3:36 presotto
1997-04-21  1:03 David
1997-04-20 16:12 miller
1997-04-19 16:49 Magnus
1997-04-19 10:22 Digby
1997-04-19  4:59 chad
1997-04-19  4:09 ozan
1997-04-19  3:52 Berry
1997-04-19  1:51 David
1997-04-19  0:56 Rich
1997-04-19  0:41 Rich
1997-04-18 21:19 Paul
1997-04-18 21:01 Digby
1997-04-18 20:47 Digby
1997-04-18 16:39 presotto
1997-04-18 16:10 Eric
1997-04-18 16:07 Eric
1997-04-18 15:57 Eric
1997-04-18 15:51 Eric
1997-04-18 15:37 Dean
1997-04-18 15:14 forsyth
1997-04-18 13:54 Brandon
1997-04-18  9:50 Andrew
1997-04-18  8:10 Digby
1997-04-18  8:04 Digby
1997-04-18  7:58 Steve_Kilbane
1997-04-18  7:52 Steve_Kilbane
1997-04-18  7:15 Nigel
1997-04-18  5:57 Nickolay
1997-04-18  5:49 Brandon
1997-04-18  3:15 Steve
1997-04-18  0:33 Pete
1997-04-17 23:43 Eric
1997-04-17 23:19 Eric
1997-04-17 21:55 Eric
1997-04-17 21:46 Rich
1997-04-17 21:45 Rich
1997-04-17 18:43 Eric
1997-04-17 18:17 forsyth
1997-04-17 18:13 forsyth
1997-04-17 17:59 Bodet
1997-04-17 17:07 Pete
1997-04-17 16:33 Rich

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=19970418045904.KM5cV9fXFb_s7BKsyKoAEhKWEJSmo2Ip4cP2iQpUh2E@z \
    --to=jmk@plan9.bell-labs.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 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).