Xref: utzoo comp.unix.ultrix:2411 comp.windows.x:16225 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!sun-barr!decwrl!vixie From: vixie@decwrl.dec.com (Paul A Vixie) Newsgroups: comp.unix.ultrix,comp.windows.x Subject: Re: VaxStation 3520 MicroCode -- whereizit? Message-ID: Date: 29 Dec 89 04:57:10 GMT References: <35136@cornell.UUCP> Sender: news@decwrl.dec.com Organization: DEC Western Research Lab Lines: 24 In-reply-to: kowalski@svax.cs.cornell.edu's message of 13 Dec 89 23:00:16 GMT Sorry, can't help with your first question, I don't know. >> NEXT: >> the 3520 is a 2 processor machine, but I can't tell. I mean, >> it sez that "processor b is started," but a ps gives no indication of >> parallelization, even at the processor level. On a Gould, a ps will >> tell you which cpu your job's on. So what gives? Does the machine >> run both cpus or not really. On Ultrix versions up through 3.1, the parallel processing isn't visible through normal means. You can see it with iostat and you can certainly feel the difference if you run a GNU Make in parallel mode :-). The multiprocessor support gets a lot better in 4.0, but until then all it's really doing is allocating a processor at schedule-time -- EACH schedule time. Your job doesn't get "allocated" to a processor. Even in 4.0 it won't be "allocated", it's a many-processors-to-many-jobs mapping that takes place continuously. Paul Vixie DEC WRL -- Paul Vixie Work: vixie@decwrl.dec.com decwrl!vixie +1 415 853 6600 Play: paul@vixie.sf.ca.us vixie!paul +1 415 864 7013