9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: forsyth@plan9.cs.york.ac.uk forsyth@plan9.cs.york.ac.uk
Subject: General questions...
Date: Mon, 19 Aug 1996 23:51:26 +0100	[thread overview]
Message-ID: <19960819225126.3IE6FCRsf58gb3eJc_RIbtPMzOyxWKWGPk0D-xTqY8Q@z> (raw)

>>	2.  Will the sparc10 cpu server code be able to make use of
>>		multiple processors on my Sparc20? (say adding another
>>		60Mhz SuperSparc..?)

not as it stands: the ss10 mmu.c is based on my mmu.c for the lx/classic,
which in turn was based on a mixture of the next and ss mmu.c files.
it lacks interlocks, at least.  a better approach on a multiprocessor might be to
adopt the strategy of power/mmu.c and chm/mmu.c: they use a stunningly elegant
distributed garbage collection algorithm (and very little code)
to manage a collection of virtual contexts across the TLBs of a multiprocessor.

>>	3.  Are there any commercial SCSI Worm devices in a "reasonable"
>>		price range that I could use on the pentium fileserver?
>>		I don't think I can afford the 350GB sony that att uses,
>>		but I dont need 350 gigs anyways....

HP had some jukeboxes that seemed promising (a reasonable amount of storage
without a huge price tag), but are probably still a little expensive for home use.
then again, if you're considering FDDI you might be able to afford them.
i've read that HP has pulled out of the disc business, but i'd be surprised if that
included WORMS.

you'll probably need to change the file server code slightly to support something
other than the Sonys.




             reply	other threads:[~1996-08-19 22:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-08-19 22:51 forsyth [this message]
  -- strict thread matches above, loose matches on Subject: below --
1996-08-20 14:42 forsyth
1996-08-20  6:57 Nigel
1996-08-19 23:30 philw
1996-08-19 20:47 Photon

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=19960819225126.3IE6FCRsf58gb3eJc_RIbtPMzOyxWKWGPk0D-xTqY8Q@z \
    --to=forsyth@plan9.cs.york.ac.uk \
    /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).