> On Feb. 12, 2017, 4:50 a.m., Jieming Yin wrote:
> > We also observed long packet delay in heavy-traffic workloads. Just
> > curious, how much does this fix improve?
I noticed the problem when the deadlock threshold that was added recently
started getting triggered at very high injection rate
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/3809/
---
Review request for Default, Brad Beckmann, Jieming Yin, Matthew Poremba, and
Onur Ka
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/3777/#review9417
---
This no longer applies cleanly. I think it's probably something I screwed
> On Feb. 11, 2017, 5:43 p.m., Andreas Hansson wrote:
> > I think this one did not get committed. Is that right?
Oops. That was an accidental oversight. Thanks for pointing it out.
- Jason
---
This is an automatically generated e-mail.
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/3777/#review9415
---
Ship it!
I think this one did not get committed. Is that right?
- Andre
changeset 79c3f6a60392 in /z/repo/gem5
details: http://repo.gem5.org/gem5?cmd=changeset;node=79c3f6a60392
description:
mem: fix printing of 1st cache tags line
Rather than having the 1st line on the Log line and every other line on
its
own, add a new line to have a common
