FS#253 — The bus object constantly schedules itself for one bus cycle later if it has something on it's retry
Attached to Project— M5 Bugs
Opened by Ali Saidi (saidi) - Monday, 07 May 2007, 01:04PM
Last edited by Ali Saidi (saidi) - Friday, 11 April 2008, 01:47PM
Opened by Ali Saidi (saidi) - Monday, 07 May 2007, 01:04PM
Last edited by Ali Saidi (saidi) - Friday, 11 April 2008, 01:47PM
| Bug | |
| Memory System | |
| New | |
| No-one | |
| All |
| High | |
| Normal | |
| 1.1 | |
| 2.0 | |
| Undecided | |
 |
The bus object constantly schedules itself for one bus cycle later if it has something on it's retry list. This means that in high latency situations the bus is doing a lot of useless work.
This task depends upon
This task blocks these from closing
This may be a duplicate of 270 even though it says "one bus cycle" and not "one tick"... or is this a different bug where it's checking every bus cycle but could wait multiple bus cycles?
It's a different bug. If there is something on the retry queue the bus never actually waits for the retry before trying to reschedule itself to send out the data, but instead schedules itself constantly to do no work.
Gabe looked into this, i don't know if it's fixed currently or not. It's purely a performance issue, but it would be nice to fix.