2015
DOI: 10.1007/978-3-319-16214-0_7
|View full text |Cite
|
Sign up to set email alerts
|

Preemptive Hardware Multitasking in ReconOS

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
19
0

Year Published

2016
2016
2021
2021

Publication Types

Select...
4
3
2

Relationship

0
9

Authors

Journals

citations
Cited by 42 publications
(19 citation statements)
references
References 8 publications
0
19
0
Order By: Relevance
“…This is because the state may be spread out across Flip-Flops, Logic Cells and BRAMs. Saving and restoring the complete state for such a case can easily take anywhere from microseconds to milliseconds [69] in addition to partial reconfiguration latency. Further, the hardware support required for a preemptable hardware module tends to be rather restrictive and very target specific.…”
Section: Schedulingmentioning
confidence: 99%
“…This is because the state may be spread out across Flip-Flops, Logic Cells and BRAMs. Saving and restoring the complete state for such a case can easily take anywhere from microseconds to milliseconds [69] in addition to partial reconfiguration latency. Further, the hardware support required for a preemptable hardware module tends to be rather restrictive and very target specific.…”
Section: Schedulingmentioning
confidence: 99%
“…Scheduling is the key to multi-tenancy, but the conventional techniques (preemptive, non-preemptive, and cooperative) cannot be used for FPGA accelerators unchanged, as the state of the system that needs to be saved and restored is not trivial. The state data may be distributed across all different resources on FPGA fabric and one single operation to save or restore the state can add micro to milli seconds to the latency [98]. However, the requirement of mandatory dedicated hardware module can be avoided, as in [99], where such jobs are either blocked or sent back to CPU to perform.…”
Section: Schedulingmentioning
confidence: 99%
“…Like full bitstreams, partial bitstreams contain a header and a footer; these sections serve the same purposes as before. However, if the RESET AFTER RECONFIG property is set on the PR region, as is usually the case, CFG CLB frames precede the other configuration frames [24]. CFG CLB frames are mostly undocumented by Xilinx, but a comparison of different partial bitstreams reveals that the contents of this section of the bitstream differ for different PR regions [25].…”
Section: Partial Bitstream Generationmentioning
confidence: 99%