On Wed, 08 Mar 2006 10:14:02 -0600
Greg Oster <oster@cs.usask.ca> wrote:

>
> 
> For the record, the above program runs without any problems on a
> Sun V40z with 4 of these little guys:
> 
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: AMD Opteron(tm) Processor 850, 2393.34 MHz
> cpu0: features: e7dbfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR>
> cpu0: features: e7dbfbff<PGE,MCA,CMOV,PAT,PSE36,MPC,NOX,MMXX,MMX>
> cpu0: features: e7dbfbff<FXSR,SSE,SSE2,LONG,3DNOW2,3DNOW>
> cpu0: I-cache 64 KB 64B/line 2-way, D-cache 64 KB 64B/line 2-way
> cpu0: L2 cache 1 MB 64B/line 16-way
> cpu0: ITLB 32 4 KB entries fully associative, 8 4 MB entries fully associative
> cpu0: DTLB 32 4 KB entries fully associative, 8 4 MB entries fully associative
> cpu0: calibrating local timer
> cpu0: apic clock running at 199 MHz
> cpu0: 16 page colors
> 
> Even ran 4 concurrent copies of the program for a while, with zero 
> problems/hangs/whatever...
> 
There's some chance that running 4 copies will make it less likely -- the
scheduler will time-share them, so you may not get whatever the deadly
pattern is.  (That's my guess about why Windows takes longer tha Linux -- a
different scheduler.) 


		--Steven M. Bellovin, http://www.cs.columbia.edu/~smb