2014 International Conference on ReConFigurable Computing and FPGAs (ReConFig14) 2014
DOI: 10.1109/reconfig.2014.7032516
|View full text |Cite
|
Sign up to set email alerts
|

Enabling partial reconfiguration for coprocessors in mixed criticality multicore systems using PCI express single-root I/O virtualization

Abstract: Especially in complex system-of-systems scenarios, where multiple high-performance or real-time processing functions need to co-exist and interact, reconfigurable devices together with virtualization techniques show considerable promise to increase efficiency, ease integration and maintain functional and non-functional properties of the individual functions. In this paper, we propose a concept that leverages the advantages of FPGA's partial reconfiguration in heterogeneous mixed criticality multicore systems. … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

1
5
0

Year Published

2015
2015
2023
2023

Publication Types

Select...
6
2
1

Relationship

0
9

Authors

Journals

citations
Cited by 13 publications
(6 citation statements)
references
References 8 publications
1
5
0
Order By: Relevance
“…We evaluated two accelerated image processing applications, which we combine to produce three execution scenarios: (a) multiple instances of a single application share all the accelerators, (b) multiple instances of both applications share the common accelerators, and (c) with multiple threads that do not share any of the hardware accelerators. Our results show that (1) despite its generality, RACOS can achieve high throughput rates, close to the maximum reported in bibliography [38], and (much) better reconfiguration throughput reaching 177 partial reconfigurations per second for our platform and benchmark accelerators, and (2) that RACOS' flexibility comes at a very small resource cost (about 3% of a medium sized FPGA), comparable or better than the current state of the art [39].…”
Section: Discussionsupporting
confidence: 76%
“…We evaluated two accelerated image processing applications, which we combine to produce three execution scenarios: (a) multiple instances of a single application share all the accelerators, (b) multiple instances of both applications share the common accelerators, and (c) with multiple threads that do not share any of the hardware accelerators. Our results show that (1) despite its generality, RACOS can achieve high throughput rates, close to the maximum reported in bibliography [38], and (much) better reconfiguration throughput reaching 177 partial reconfigurations per second for our platform and benchmark accelerators, and (2) that RACOS' flexibility comes at a very small resource cost (about 3% of a medium sized FPGA), comparable or better than the current state of the art [39].…”
Section: Discussionsupporting
confidence: 76%
“…The technique can provide strong virtualization guarantees [36,37], but hardware-level resource management is inflexible and unevolvable: current implementations are trivially vulnerable to fragmentation and unfairness pathologies that cannot be changed. Moreover, evidence is scant that broad SR-IOV support will emerge for accelerators: only two current GPUs support it [4,46], none of the TPUs we evaluate support it; and SR-IOV interface IP blocks from FPGA vendors (used by [47,76,96,108]) do not implement resource management. We do not expect this to change any time soon: SR-IOV requires significant engineering effort vendors are not incentivized to invest.…”
Section: Existing Accelerator Virtualization Techniquesmentioning
confidence: 99%
“…Although our approach addresses similar applications, our strategy prioritizes the maximum area reuse of RPs while reducing the number of reconfigurations on a PCIe-based FPGA. Despite the fact that none of the mentioned works uses PCIe, PR through PCIe has been already targeted in [17,18]. Our proposed NE presents a more complex application which benefits from the current state-of-the-art technology [19].…”
Section: Related Workmentioning
confidence: 99%
“…for ∈ RP do (8) for ∈ Size( ) do (9) if Config( temp ( )) = Config( ( )) then (10) node [ ] ← InsertConfigInRP( ( ), ); (11) node [ ] ← MarkAsConfigured(); (12) ← RemoveConfigfromList( , ); (13) break; (14) end (15) end (16) end (17) if…”
Section: Schedulingmentioning
confidence: 99%