2019 IEEE Real-Time and Embedded Technology and Applications Symposium (RTAS) 2019
DOI: 10.1109/rtas.2019.00035
|View full text |Cite
|
Sign up to set email alerts
|

Achieving Stagnation-Free Intermittent Computation with Boundary-Free Adaptive Execution

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
16
0

Year Published

2019
2019
2024
2024

Publication Types

Select...
5
4

Relationship

1
8

Authors

Journals

citations
Cited by 29 publications
(16 citation statements)
references
References 53 publications
0
16
0
Order By: Relevance
“…1 These systems require perfect energy prediction to not get corrupted. Any changes in, for example, capacitor size [19], power consumption due to peripheral use, or harvested energy, will lead to incorrect predictions and therefore corruption. e.g.…”
Section: Gaming Through Power Failuresmentioning
confidence: 99%
See 1 more Smart Citation
“…1 These systems require perfect energy prediction to not get corrupted. Any changes in, for example, capacitor size [19], power consumption due to peripheral use, or harvested energy, will lead to incorrect predictions and therefore corruption. e.g.…”
Section: Gaming Through Power Failuresmentioning
confidence: 99%
“…From the publication of a first framework supporting intermittently-powered devices, Mementos [109]-voltage threshold-triggered checkpoining system, more efficient checkpoint systems are being published. These include Hibernus++ [8] and QuickRecall [57] (just like Mementos, both hardware-activated chceckpoints), Chinchilla [82], Rachet [137] and HarvOS [11] (all three compiler-instrumented checkpoints), TICS (time-aware checkpoints) [68], TotalRecall (checkpoints using volatile memory) [144], Elastin (adaptive checkpoints) [19], DICE (differential checkpoints) [2,3] and WhatsNext (checkpointing augmented with approximate computing) [35]. A second class of systems include runtimes based on specially instrumented code (by form for a task) such as Dino [78], Chain [22], Alpaca [81], MayFly [45], InK [150], Coati [110], CoSpec [20] and Coala [84].…”
Section: :26 • De Winkel Et Almentioning
confidence: 99%
“…Lastly, in an approach closer to compilerdirected approaches than to other hardware-directed approaches, Clank [13] inserts in-hardware idempotence monitors in the memory hierarchy to better identify idempotence violations (compared to Ratchet) and to buffer idempotencebreaking writes to maximally delay checkpoints. Elastin [3] extends on the idea of Clank, but at page granularity, which is used by more complex systems.…”
Section: 22mentioning
confidence: 99%
“…However, due to the batteryless nature, energy harvesting systems suffer unpredictable frequent power failure and thus require some form of crash consistency which must be lightweight; otherwise checkpointing/restoring consistent program states across the failure can limit forward progress by consuming hard-won energy. Thus, existing systems [3,11,12,21,22,50,70] have been designed with byte-addressable non-volatile memory (NVM), where data are immediately persisted and thus recoverable at the cost of long latency. While volatile write-back caches can hide the store latency and improve performance with a load hit exploiting data locality, they have been assumed to be not viable or at least challenging in energy harvesting systems.…”
Section: Introductionmentioning
confidence: 99%