scons: `build/ALPHA_MOESI_hammer/tests/opt/quick/fs' is up to date.
scons: `build/ALPHA_MESI_CMP_directory/tests/opt/quick/fs' is up to date.
scons: `build/ALPHA_MOESI_CMP_directory/tests/opt/quick/fs' is up to date.
scons: `build/ALPHA_MOESI_CMP_token/tests/opt/quick/fs' is up to date.
scons:
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/2000/
---
(Updated Oct. 8, 2013, 1:42 p.m.)
Review request for Default.
Changes
---
Hi Brad,
I am actually inclined to say that the packet queue should only be used in
simple devices to model pipeline latency, and that the value 100 is
already too large. The only times I've hit this limit is when something in
the model is broken and not reacting properly. Recently, we switched
On Wed, 25 Sep 2013, Andreas Hansson wrote:
Hi Nilay,
I'm afraid I won't have time to do that until next week sometime.
In the meanwhile I have re-verified that the regressions are indeed
getting 19% slower (by disabling your patch again). ~13hr with and ~11hr
without.
Andreas, were you
Hi Nilay,
Unfortunately I haven't found the time to dig into this yet.
I only have the output from last nights regression, and thus not with and
without your patch. I'll take a snapshot and compare, although I suspect
the individual runs vary quite a bit.
Have you attempted any further
Yes, Andreas the Ruby interface uses the PacketQueue for the response packets
after your changesets 8742 and 8914 (note the modifications to RubyPort.hh).
Before you checked in these changes, the RubyPort used a simple timing port for
response packets. I believe you checked in these changes
