Early performance results from the prototype CHERI ARM Morello microarchitecture
ctsrd-cheri.github.io
Early performance results from the prototype CHERI ARM Morello microarchitecture
1–10 of 20 posts
Re: Early performance results from the prototype CHERI ARM Morello microarchitecture
#2What is this documentation theme? Can someone enlighten me?
Re: Early performance results from the prototype CHERI ARM Morello microarchitecture
#3What is this documentation theme? Can someone enlighten me?
It is produced by mdBook
https://rust-lang.github.io/mdBook/
Re: Early performance results from the prototype CHERI ARM Morello microarchitecture
#4The depressing thing is looking at the performance cost of so many of these mitigations that are fundamentally due to the use of unsafe languages.
It results in a somewhat pernicious effect: a person can compare their unsafe language to a safe one and say “see it’s faster” because the safe language is being subject to the same hardware costs but they’re unnecessary.
The lack of memory safety in many core languages means we take mitigations that increase memory usage, increase processor complexity, and reduce overall performance.
Re: Early performance results from the prototype CHERI ARM Morello microarchitecture
#5Is this an attempt to bring memory safety to C and similar unsafe languages? They really need an executive summary and overview.
Re: Early performance results from the prototype CHERI ARM Morello microarchitecture
#6The depressing thing is looking at the performance cost of so many of these mitigations that are fundamentally due to the use of unsafe languages. It results in a somewhat pernicious effect: a person can compare their unsafe language to a safe one and say “see it’s faster” because the safe language is being subject to the same hardware costs but they’re unnecessary. The lack of memory safety in many core languages me…
CHERI enforces safety in hardware. No amount of language safety can prevent exploits from being forged right out of machine code.
Re: Early performance results from the prototype CHERI ARM Morello microarchitecture
#7Is this an attempt to bring memory safety to C and similar unsafe languages? They really need an executive summary and overview.
Yes it is.
Re: Early performance results from the prototype CHERI ARM Morello microarchitecture
#8Conclusion: it is reasonable to project that the goal of 2%-3% overhead for deterministic spatial and referential memory safety is achievable.
Re: Early performance results from the prototype CHERI ARM Morello microarchitecture
#9The depressing thing is looking at the performance cost of so many of these mitigations that are fundamentally due to the use of unsafe languages. It results in a somewhat pernicious effect: a person can compare their unsafe language to a safe one and say “see it’s faster” because the safe language is being subject to the same hardware costs but they’re unnecessary. The lack of memory safety in many core languages me…
CHERI enforces safety in hardware. No amount of language safety can prevent exploits from being forged right out of machine code.
CHERI gives you greater granularity over memory access it doesn’t magic away security vulnerabilities.
But that doesn’t negate what I stated: there’s a massive amount of complexity, and significant performance costs of all these features. They’re needed because the prevalence of unsafe code means we need a global enforcement mechanism which means hardware.
Hence we take a real and permanent cost in hardware that applies to all code on the system. The cost is hardware complexity, runtime performance, and memory, and it is borne by all software on the system.
Re: Early performance results from the prototype CHERI ARM Morello microarchitecture
#10The depressing thing is looking at the performance cost of so many of these mitigations that are fundamentally due to the use of unsafe languages. It results in a somewhat pernicious effect: a person can compare their unsafe language to a safe one and say “see it’s faster” because the safe language is being subject to the same hardware costs but they’re unnecessary. The lack of memory safety in many core languages me…
[deleted]