I could obtain the blackscholes performance within 3hrs using
MESI_Two_Level. However, MOESI_CMP_directory is very slow and requires more
than 3hrs before starting the ROI section.
I recompiled the program as you mentioned and I found the system is showing
some INFO message through the telnet localhost (However, I couldn't find
such INFO message in case of blackscholes) and still running for about 24
hrs-
Linux version: Scientific Linux release 6.1 (Carbon)
# scons FULL_SYSTEM=1 build/ALPHA/gem5.fast RUBY=true
PROTOCOL=MESI_Two_Level
# ./build/ALPHA/gem5.fast configs/example/fs.py --cpu-type=timing
--script=script/vips_16c_simsmall.rcS --mem-size=1GB --num-cpus=16 --ruby
--mesh-rows=4 --network=garnet2.0 --topology=Mesh_XY --caches --l2cache
--l2_size=16MB --num-dirs=16 --num-l2=16 --l1d_size=64kB --l1i_size=64kB
--l1d_assoc=2 --l1i_assoc=2
--disk-image=/home1/xxx/gem5/system/alpha/m5_system_2.0b3/disks/linux-parsec-2-1-m5.img
INFO: task vips:894 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
vips D 0000000000000000 0 894 871
fffffc003f073da8 0000000000000001 fffffc000036e078 fffffc003f3ce740
00000000003b9ac9 0000000000000003 fffffc000035a16c 0000000000000000
fffffc000036ddc0 fffffc000086bf40 fffffc000081bf40 fffffc000035a0f0
fffffc0000819040 fffffc003f063ea8 fffffc0000000063 fffffc0000811b80
fffffc00008113b8 fffffc00003111d0 fffffc00003111e8 fffffc003f05fd40
fffffc003f05fce8 fffffc0000821760 0000000000000000 0000000000000000
Trace:
[<fffffc000036e078>] watchdog+0x2b8/0x320
[<fffffc000035a16c>] kthread+0x7c/0xd0
[<fffffc000036ddc0>] watchdog+0x0/0x320
[<fffffc000035a0f0>] kthread+0x0/0xd0
[<fffffc00003111d0>] kernel_thread+0x10/0x90
[<fffffc00003111e8>] kernel_thread+0x28/0x90
Thanks in advance.
F. A. Faisal
On Wed, Jun 21, 2017 at 10:35 PM, Krishna, Tushar <tus...@ece.gatech.edu>
wrote:
> Hi Faisal,
> I see you are running a 256 threaded vips on the 16 core system. Maybe try
> a 16 threaded version?
> Also, can you try running without garnet -- I'm curious to see how long
> the benchmarks take in that case.
>
> Cheers,
> Tushar
>
>
> On Jun 21, 2017, at 3:07 AM, F. A. Faisal <dipu.7...@gmail.com> wrote:
>
> Dear All,
>
> I tried to simulate the Parsec 2.1 benchmarks with garnet 2.0.
> I found that other than Blackscholes, rest of benchmarks are taking
> several days (and still executing) and even I tried with increasing the
> <nthread> num of benchmarks, which actually don't have too much effect.
> However, the actual executions time should be in few hours.
> Please help me to increase the execution rate and how to know, how many
> percentage of benchmark program is being finished.
>
> My simlutation conditions-
>
> # scons FULL_SYSTEM=1 build/ALPHA/gem5.fast RUBY=true
> PROTOCOL=MESI_Two_Level
>
> # ./build/ALPHA/gem5.fast configs/example/fs.py --cpu-type=timing
> --script=script/vips_256c_simsmall.rcS --num-cpus=16 --mem-size=1GB
> --ruby --mesh-rows=4 --network=garnet2.0 --topology=Mesh_XY --caches
> --l2cache --l2_size=1MB --num-dirs=16 --num-l2=16 --l1d_size=32kB
> --l1i_size=32kB --l1d_assoc=2 --l1i_assoc=2 --disk-image=/home1/faisal/
> gem5/system/alpha/m5_system_2.0b3/disks/linux-parsec-2-1-m5.img
>
> Thanks in advance...
>
> Best regards,
>
> F. A. Faisal
>
> _______________________________________________
> gem5-users mailing list
> gem5-users@gem5.org
> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>
>
> _______________________________________________
> gem5-users mailing list
> gem5-users@gem5.org
> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
