Searched hist:11092 (Results 1 - 4 of 4) sorted by relevance
| /gem5/src/mem/ruby/network/simple/ | ||
| H A D | PerfectSwitch.hh | 11092:a51ef09e3a78 Sat Sep 12 17:16:00 EDT 2015 Nilay Vaish <nilay@cs.wisc.edu> ruby: simple network: store Switch* in PerfectSwitch and Throttle There are two reasons for doing so: a. provide a source of clock to PerfectSwitch. A follow on patch removes sender and receiver pointers from MessageBuffer means that the object owning the buffer should have some way of providing timing info. b. schedule events. A follow on patch removes the consumer class. So the PerfectSwitch needs some EventManager object to schedule events on its own. |
| H A D | Throttle.hh | 11092:a51ef09e3a78 Sat Sep 12 17:16:00 EDT 2015 Nilay Vaish <nilay@cs.wisc.edu> ruby: simple network: store Switch* in PerfectSwitch and Throttle There are two reasons for doing so: a. provide a source of clock to PerfectSwitch. A follow on patch removes sender and receiver pointers from MessageBuffer means that the object owning the buffer should have some way of providing timing info. b. schedule events. A follow on patch removes the consumer class. So the PerfectSwitch needs some EventManager object to schedule events on its own. |
| H A D | Throttle.cc | 11092:a51ef09e3a78 Sat Sep 12 17:16:00 EDT 2015 Nilay Vaish <nilay@cs.wisc.edu> ruby: simple network: store Switch* in PerfectSwitch and Throttle There are two reasons for doing so: a. provide a source of clock to PerfectSwitch. A follow on patch removes sender and receiver pointers from MessageBuffer means that the object owning the buffer should have some way of providing timing info. b. schedule events. A follow on patch removes the consumer class. So the PerfectSwitch needs some EventManager object to schedule events on its own. |
| H A D | PerfectSwitch.cc | 11092:a51ef09e3a78 Sat Sep 12 17:16:00 EDT 2015 Nilay Vaish <nilay@cs.wisc.edu> ruby: simple network: store Switch* in PerfectSwitch and Throttle There are two reasons for doing so: a. provide a source of clock to PerfectSwitch. A follow on patch removes sender and receiver pointers from MessageBuffer means that the object owning the buffer should have some way of providing timing info. b. schedule events. A follow on patch removes the consumer class. So the PerfectSwitch needs some EventManager object to schedule events on its own. |
Completed in 33 milliseconds