[Gems-users] ruby possibly hanging on 64p MSI_MOSI_CMP_directory

["Brad Moore" <brad.t.moore@xxxxxxxxx>]

Hey all,

I'm currently running a benchmark that has been executing for over 24hrs.  I haven't successfully executed it with simics + ruby, but I have executed it with simics and it took under 5 minutes.  I'm trying to figure out if it's just going to take this long, or if I may have done something that would cause ruby to hang silently.

64 process Sarek machine running Solaris 9.

Before compiling MSI_MOSI_CMP_directory, I edited rubyconfig.defaults:
g_NUM_PROCESSORS: 64
g_NUM_L2_BANKS: 8
g_NUM_MEMORIES: 1
g_PROCS_PER_CHIP: 64

And I created a file, NUCA_Procs-64_ProcsPerChip-64_L2Banks-8_Memories-1.txt
After that, I went into ./ruby and called built MSI_MOSI_CMP_directory.


Now, if it is just taking too long...  Could I reduce the memory requirements of the simulation by reducing the memory size parameter to ruby?  Does that parameter have to be equivalent to the corresponding simics parameter?

Thanks!
-Brad