Proceedings of EUROMICRO 96. 22nd Euromicro Conference. Beyond 2000: Hardware and Software Design Strategies
DOI: 10.1109/eurmic.1996.546476
|View full text |Cite
|
Sign up to set email alerts
|

Real-time scheduling co-processor in hardware for single and multiprocessor systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
15
0

Publication Types

Select...
4
3

Relationship

0
7

Authors

Journals

citations
Cited by 11 publications
(19 citation statements)
references
References 6 publications
0
15
0
Order By: Relevance
“…The AMU, supporting four accelerators and 32job types (see Section 5.2), required 3300 standard equivalent gates, ignoring the 512 byte RAM . This is considerably smaller than the RTU scheduler [9], whose area, as shown in Table 1 is 25000 gates. The AMU's maximum operating frequency was 526 MHz.…”
Section: Implementation Environmentmentioning
confidence: 89%
See 1 more Smart Citation
“…The AMU, supporting four accelerators and 32job types (see Section 5.2), required 3300 standard equivalent gates, ignoring the 512 byte RAM . This is considerably smaller than the RTU scheduler [9], whose area, as shown in Table 1 is 25000 gates. The AMU's maximum operating frequency was 526 MHz.…”
Section: Implementation Environmentmentioning
confidence: 89%
“…The real-time service providing co-processor Real-Time Unit (RTU) [9] supports static and priority-based scheduling. The SSCoP real-time scheduling co-processor [8] supports both static and online scheduling with different policies; it assumes that tasks are non-preemptable and have precedence constraints .…”
Section: Related Workmentioning
confidence: 99%
“…the maximum number of items that can be sorted). The most popular architectures include FIFO with MUX Tree [10,11,15,21], Shift Registers [18,20,22,23], DP RAM Heapsort [19] and Systolic Array [24][25][26][27][28]33].…”
Section: Related Work On Sorting Architecturesmentioning
confidence: 99%
“…The FIFO approach is the least scalable in terms of critical path length due to the complexity of the MUX Tree part, which contains too long critical path. It is also very inefficient in terms of chip area cost [10,11,15,21].…”
Section: Related Work On Sorting Architecturesmentioning
confidence: 99%
“…One solution uses the EDF algorithm too but with the maximum number of tasks being only 64, 25 and the other approach uses priorities instead of deadlines, which is less e±cient for realtime systems in terms of CPU utilization. 26 There are other solutions based on priorities or static scheduling [27][28][29] as well. These solutions are suitable for systems consisting of hard real-time tasks only.…”
Section: Related Workmentioning
confidence: 99%