The Performance Impact To POWER9's Eager L1d Cache Flushing Fix
Collapse
X
-
It's not that bad for the fix. This is L1 data flushing, I would have imagined 30%+ problems.
-
-
I remember that Michael once did a benchmark shootout between comparable Server-CPUs across all relevant ISA's - a follow-on could be interesting as performance enhancements and new security patches emerged and new CPU generations became available.
Leave a comment:
-
-
I was expecting the performance drop to be even worse. That is pretty bad, but not catastrophically bad.
Plus many syscall-light workloads are not impacted, as expected.
Leave a comment:
-
-
Originally posted by ezekrb5 View PostAt least they moved quickly and fixed this very soon.
People bash intel for the security flaws but intel did move quite fast to fix them.
For a server I don't value raw performance as much as I do value security, patches and being a responsible company.
Leave a comment:
-
-
At least they moved quickly and fixed this very soon.
People bash intel for the security flaws but intel did move quite fast to fix them.
For a server I don't value raw performance as much as I do value security, patches and being a responsible company.
Leave a comment:
-
-
The Performance Impact To POWER9's Eager L1d Cache Flushing Fix
Phoronix: The Performance Impact To POWER9's Eager L1d Cache Flushing Fix
Last week a new vulnerability was made public for IBM POWER9 processors resulting in a mitigation of the processor's L1 data cache needing to be flushed between privilege boundaries. Due to the possibility of local users being able to obtain data from the L1 cache improperly when this CVE is paired with other side channels, the Linux kernel for POWER9 hardware is flushing the L1d on entering the kernel and on user accesses. Here are some preliminary benchmarks looking at how this security change impacts the overall system performance.
Tags: None
-
Leave a comment: