Searched hist:13736 (Results 1 - 4 of 4) sorted by relevance
| /gem5/src/mem/ruby/network/garnet2.0/ | ||
| H A D | SwitchAllocator.cc | 13736:e678df1f0bf2 Fri Feb 22 17:43:00 EST 2019 Srikant Bharadwaj <srikant.bharadwaj@amd.com> ruby: Fix garnet's round robin arbitration for vc selection Garnet utilizes round robin policy to select a VC for transmission ar Network Interface and Routers. The current logic for round robin is only fair if all the virtual networks are active at a given router. If the router or network interface is not receiving traffic in from any vnet then the priority is always taken up by the next vnet in numerically (or loops back to 0). This fix changes the way we perform round robin arbitration. When a VC is selected in a cycle, the round robin pointer is set to the VC next to it and is iterated from there on. If any VC does not have a flit in a given cycle, it will lose its turn until the next round. At maximum traffic this will model round robin correctly even if a certain VNET is not active at that unit. Change-Id: I9bf805221054f9f25bee14b57ff521f4ce4ca980 Reviewed-on: https://gem5-review.googlesource.com/c/16688 Reviewed-by: Jieming Yin <Jieming.Yin@amd.com> Maintainer: Jason Lowe-Power <jason@lowepower.com> |
| H A D | NetworkInterface.cc | 13736:e678df1f0bf2 Fri Feb 22 17:43:00 EST 2019 Srikant Bharadwaj <srikant.bharadwaj@amd.com> ruby: Fix garnet's round robin arbitration for vc selection Garnet utilizes round robin policy to select a VC for transmission ar Network Interface and Routers. The current logic for round robin is only fair if all the virtual networks are active at a given router. If the router or network interface is not receiving traffic in from any vnet then the priority is always taken up by the next vnet in numerically (or loops back to 0). This fix changes the way we perform round robin arbitration. When a VC is selected in a cycle, the round robin pointer is set to the VC next to it and is iterated from there on. If any VC does not have a flit in a given cycle, it will lose its turn until the next round. At maximum traffic this will model round robin correctly even if a certain VNET is not active at that unit. Change-Id: I9bf805221054f9f25bee14b57ff521f4ce4ca980 Reviewed-on: https://gem5-review.googlesource.com/c/16688 Reviewed-by: Jieming Yin <Jieming.Yin@amd.com> Maintainer: Jason Lowe-Power <jason@lowepower.com> |
| /gem5/src/unittest/ | ||
| H A D | SConscript | 13360:a2254720ecf3 Tue Oct 23 19:08:00 EDT 2018 Andreas Sandberg <andreas.sandberg@arm.com> tests: Convert AddrRangeMap unit test to a GTest Change-Id: Ifeb0b57c0cda77706691286f78325e50edb31c0d Signed-off-by: Andreas Sandberg <andreas.sandberg@arm.com> Reviewed-on: https://gem5-review.googlesource.com/c/13736 Reviewed-by: Jason Lowe-Power <jason@lowepower.com> Reviewed-by: Giacomo Travaglini <giacomo.travaglini@arm.com> |
| /gem5/src/base/ | ||
| H A D | SConscript | 13360:a2254720ecf3 Tue Oct 23 19:08:00 EDT 2018 Andreas Sandberg <andreas.sandberg@arm.com> tests: Convert AddrRangeMap unit test to a GTest Change-Id: Ifeb0b57c0cda77706691286f78325e50edb31c0d Signed-off-by: Andreas Sandberg <andreas.sandberg@arm.com> Reviewed-on: https://gem5-review.googlesource.com/c/13736 Reviewed-by: Jason Lowe-Power <jason@lowepower.com> Reviewed-by: Giacomo Travaglini <giacomo.travaglini@arm.com> |
Completed in 28 milliseconds