Hello, Biswabandan If you use M5 to simulate the PARSEC in detailed mode, it will take very long time. For canneal 4 cores simulation with simlarge input size, the simulation may last more than 30 hours. Just wait and see.
Dawei > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 14 Jun 2011 07:53:10 +0530 > From: biswabandan panda <[email protected]> > To: M5 users mailing list <[email protected]> > Subject: Re: [gem5-users] how long it takes for simulation of PARSEC > benchmarks > Message-ID: <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > it has been 20 hrs & still running? > > On Mon, Jun 13, 2011 at 9:11 PM, biswabandan panda <[email protected] > >wrote: > > > Hi, > > i was running PARSEC benchmarks like bodytrack, canneal, > > streamcluster in the ROI region after checkpoint with simsmall , but > > it was running from last 9 hrs? i just want to confirm whether it's ok or > > something is wrong somewhere? > > -- > > > > > > > > > -- > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://m5sim.org/cgi-bin/mailman/private/gem5-users/attachments/20110614/eddd030a/attachment-0001.html > > > > ------------------------------ > > Message: 2 > Date: Tue, 14 Jun 2011 08:04:34 +0530 > From: biswabandan panda <[email protected]> > To: M5 users mailing list <[email protected]> > Subject: [gem5-users] PARSEC (canneal) benchmark looping for specified > instructions? > Message-ID: <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > i was running a fresh copy of gem5, wit no changes in any part of > the code, i ran the canneal benchmark from PARSEC, it was still running for > more than 20 hours. Therefore i put the debug flags for Cache and ran it > again. Here is a snapshot of the trace which was coming from last 10 mins > or > so. I am using O3 core with GHB prefetcher turned on. Any ideas why it is > happening like this, especially PARSEC users. PLz do reply > > 2303711476500: system.cpu0.icache: ReadReq (ifetch) 6fc0 hit > 2303711476500: system.cpu0.dcache: ReadReq 1f54f838 hit > 2303711476500: system.cpu0.dcache: ReadReq 1f54f840 hit > 2303711476500: system.cpu0.dcache: ReadReq 1f54f848 hit > 2303711477000: system.cpu0.dcache: ReadReq 1f54f850 hit > 2303711477000: system.cpu0.dcache: ReadReq 1f54f858 hit > 2303711477000: system.cpu0.dcache: ReadReq 1f54f860 hit > 2303711477000: system.cpu0.dcache: ReadReq 1f54f868 hit > 2303711478000: system.cpu0.dcache: ReadReq 1f54f870 hit > 2303711478500: system.cpu0.icache: ReadReq (ifetch) 4840 hit > 2303711478500: system.cpu0.dcache: ReadReq 1f54f878 hit > 2303711478500: system.cpu0.dcache: ReadReq 1f54f880 hit > 2303711478500: system.cpu0.dcache: ReadReq 1f54f888 hit > 2303711478500: system.cpu0.dcache: ReadReq 1f54f890 hit > 2303711479000: system.cpu0.dcache: ReadReq 1f54f898 hit > 2303711486000: system.cpu0.dcache: ReadReq 1f54f8c0 hit > 2303711486000: system.cpu0.dcache: ReadReq 1f54f8c8 hit > 2303711486000: system.cpu0.dcache: ReadReq 1f54f8e8 hit > 2303711486000: system.cpu0.dcache: ReadReq 1f54f8e0 hit > 2303711486500: system.cpu0.dcache: ReadReq 1f54f8d8 hit > 2303711486500: system.cpu0.dcache: ReadReq 1f54f8d0 hit > 2303711500500: system.cpu0.icache: ReadReq (ifetch) 4880 hit > 2303711519000: system.cpu0.icache: ReadReq (ifetch) 312700 hit >
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
