Proceedings of the Ninth International Conference on Computer Supported Cooperative Work in Design, 2005. 2005
DOI: 10.1109/cscwd.2005.194321
|View full text |Cite
|
Sign up to set email alerts
|

SHUM-uCOS: A RTOS using multi-task model to reduce migration cost between SW/HW tasks

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
5
0

Year Published

2007
2007
2014
2014

Publication Types

Select...
5

Relationship

0
5

Authors

Journals

citations
Cited by 6 publications
(5 citation statements)
references
References 7 publications
0
5
0
Order By: Relevance
“…Besides the operating system extension we have reported in [12] and [13], we also focus on communication support at OS level. Table 1, the hardware task can be abstracted as hardware thread.…”
Section: Operating System Abstraction Levelmentioning
confidence: 99%
“…Besides the operating system extension we have reported in [12] and [13], we also focus on communication support at OS level. Table 1, the hardware task can be abstracted as hardware thread.…”
Section: Operating System Abstraction Levelmentioning
confidence: 99%
“…The Unified Software/Hardware multithread programming Model supporting Dynamic Reconfiguration (SHUMDR) we proposed aims at hiding the implementation details of the hardware task and offering a unified hardware/software thread view [8]. Figure 1 depicts the layered structure of SHUMDR, which consists of four abstraction levels, hardware platform on DRSoC, HTI design and adaptation, extended OS kernel and Pthreads compatible SHUMDR, from low to high respectively.…”
Section: Unified Multithread Programming Model On Drsocmentioning
confidence: 99%
“…Making use of our previous works on OS kernel extension and hardware tasks scheduling [8] [9]. In this paper, we adopt unified hardware/software multithread programming model as our solution for hybrid hardware/software task design.…”
Section: Introductionmentioning
confidence: 99%
“…The well known concept of software thread, similar as the POSIX model [3], can be applied and shift the paradigm HW thread, providing a unified transparent model [3]. The coexistence of a hybrid, software and hardware model in an operating system environment, raises concerns namely regarding an unified programming model, portability, legacy software support, suitable interface and synchronization mechanisms, communication overhead and resource optimization [4], [5], [6], eventually exacerbated in resource constrained embedded contexts. As an example of an unified hardware/software thread programming model, [4], [5], show some of the benefis of this methodology.…”
Section: Related Workmentioning
confidence: 99%
“…The coexistence of a hybrid, software and hardware model in an operating system environment, raises concerns namely regarding an unified programming model, portability, legacy software support, suitable interface and synchronization mechanisms, communication overhead and resource optimization [4], [5], [6], eventually exacerbated in resource constrained embedded contexts. As an example of an unified hardware/software thread programming model, [4], [5], show some of the benefis of this methodology. Communication overhead on a shared bus, and resource utilization are maintained low in both cases, while still offering performance improvements.…”
Section: Related Workmentioning
confidence: 99%