2020
DOI: 10.1109/tdsc.2020.3020085
|View full text |Cite
|
Sign up to set email alerts
|

Phoenix: Towards Ultra-Low Overhead, Recoverable, and Persistently Secure NVM

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
7
0

Year Published

2021
2021
2024
2024

Publication Types

Select...
6

Relationship

0
6

Authors

Journals

citations
Cited by 17 publications
(7 citation statements)
references
References 25 publications
0
7
0
Order By: Relevance
“…For updating root, like BMT, SIT has two update schemes: eager and lazy schemes [2]. The eager scheme immediately propagates the modifications of the leaf nodes to the root once the modified leaf nodes are persisted.…”
Section: E Sgx Integrity Treementioning
confidence: 99%
See 4 more Smart Citations
“…For updating root, like BMT, SIT has two update schemes: eager and lazy schemes [2]. The eager scheme immediately propagates the modifications of the leaf nodes to the root once the modified leaf nodes are persisted.…”
Section: E Sgx Integrity Treementioning
confidence: 99%
“…To propagate the modifications from leaf nodes to root, we serially hash tens of HMACs, which incurs a long latency. 2 The inconsistency between root and leaf nodes. Since the write queue in the memory controller is supported by ADR, the write queue is a persistent domain.…”
Section: G the Problem Of Updating Rootmentioning
confidence: 99%
See 3 more Smart Citations