Proceedings 14th Euromicro Conference on Real-Time Systems. Euromicro RTS 2002
DOI: 10.1109/emrts.2002.1019203
|View full text |Cite
|
Sign up to set email alerts
|

Multiprocessor DSP scheduling in system-on-a-chip architectures

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
10
0

Publication Types

Select...
3
3
2

Relationship

0
8

Authors

Journals

citations
Cited by 25 publications
(10 citation statements)
references
References 8 publications
0
10
0
Order By: Relevance
“…The locking protocol itself is a non-preemptive scheduler: it is non-preemptive since lock ownership cannot be arbitrarily revoked. Gai et al observed this in [18], where they cast the problem of scheduling a uniprocessor with a single non-preemptive digital signal processor as a synchronization problem. We also took this perspective in developing GPUSync, a single synchronization-based framework that allows us to explore every high-level category described in Sec.…”
Section: Introductionmentioning
confidence: 95%
“…The locking protocol itself is a non-preemptive scheduler: it is non-preemptive since lock ownership cannot be arbitrarily revoked. Gai et al observed this in [18], where they cast the problem of scheduling a uniprocessor with a single non-preemptive digital signal processor as a synchronization problem. We also took this perspective in developing GPUSync, a single synchronization-based framework that allows us to explore every high-level category described in Sec.…”
Section: Introductionmentioning
confidence: 95%
“…The system has been presented to be effective and efficient in several practical cases. Simple emergent behavior patterns can also be applied to the communication between multicore system ( [7]). On the other hand the system uses high levels of computing power and energy which would prevent its use for the simple robotic entities which compose the collaborative robotic environment.…”
Section: Related Workmentioning
confidence: 99%
“…It is because that the lower priority task execution in the processor is forbidden even the processor is idle, when there is a higher priority task being executed in the co-processor. On the other hand, for system utilization improvement, the forbidden condition has to be relaxed, which causes that the priority inversion goes out of control [4,5].…”
Section: Introductionmentioning
confidence: 99%