2011
DOI: 10.1016/j.jpdc.2010.10.013
|View full text |Cite
|
Sign up to set email alerts
|

CoQoS: Coordinating QoS-aware shared resources in NoC-based SoCs

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
27
0

Year Published

2013
2013
2019
2019

Publication Types

Select...
6
1

Relationship

0
7

Authors

Journals

citations
Cited by 45 publications
(27 citation statements)
references
References 35 publications
0
27
0
Order By: Relevance
“…With QoS-enforcing hardware, these techniques could coschedule workloads much more aggressively, relying on hardware to prevent interference. Hardware-based QoS enforcement: Prior work has proposed hardware schemes to partition shared resources [9,16,21,25,38,45], as well as software QoS frameworks that leverage these mechanisms to implement fairness, maximize throughput, or provide differentiated service [5,13,17,20,29,31,37,42,49,61]. However, these techniques have been developed with the goal of meeting long-term performance goals (e.g., IPC or queries per second over billions of instructions), instead of providing strict guarantees on worst-case, shortterm behavior (e.g., bounding the performance degradation of a 1 ms request).…”
Section: Quality Of Service In Cmpsmentioning
confidence: 99%
See 2 more Smart Citations
“…With QoS-enforcing hardware, these techniques could coschedule workloads much more aggressively, relying on hardware to prevent interference. Hardware-based QoS enforcement: Prior work has proposed hardware schemes to partition shared resources [9,16,21,25,38,45], as well as software QoS frameworks that leverage these mechanisms to implement fairness, maximize throughput, or provide differentiated service [5,13,17,20,29,31,37,42,49,61]. However, these techniques have been developed with the goal of meeting long-term performance goals (e.g., IPC or queries per second over billions of instructions), instead of providing strict guarantees on worst-case, shortterm behavior (e.g., bounding the performance degradation of a 1 ms request).…”
Section: Quality Of Service In Cmpsmentioning
confidence: 99%
“…In particular, CoQoS [29] and METE [49] combine cache and bandwidth partitioning mechanisms to provide endto-end performance guarantees. As discussed before, these guarantees are only on long-term performance.…”
Section: Cache Partitioning In Cmpsmentioning
confidence: 99%
See 1 more Smart Citation
“…QoS has been proposed in [14], [17], and [18] in order to combine best-effort (BE) and guaranteed throughput (GT) streams with time division multiple access (TDMA), to distinguish between traffic classes [19], [20], to map multiple use-cases in worst-case scenarios [21], [22], and to improve the access to shared resources [23], such as external memories [24], [25] in order to fulfill latency and bandwidth bounds.…”
Section: Related Workmentioning
confidence: 99%
“…Many approaches have been proposed in the past to augment NoCs with mechanisms to provide the desired QoS on the individual transaction, but they typically assume that traffic flows can be somehow categorized within a few classes with predetermined priorities [13,14]. In short, they do not face the problem of how this information can be forwarded from the programming model to physical packets.…”
Section: Introductionmentioning
confidence: 99%