On 01/05/2018 03:15, Dag-Erling Smørgrav wrote:
> Eric McCorkle writes:
>> The obvious downside is that you take a performance hit storing things
>> in non-cacheable locations, especially if you plan on doing heavy
>> computation in that memory (say, encryption/decryption). However, this
>> is al
Eric McCorkle writes:
> The obvious downside is that you take a performance hit storing things
> in non-cacheable locations, especially if you plan on doing heavy
> computation in that memory (say, encryption/decryption). However, this
> is almost certainly going to be less than the projected 30-
I've thought more about how to deal with meltdown/spectre, and I have an
idea I'd like to put forward. However, I'm still in something of a
panic mode, so I'm not certain as to its effectiveness. Needless to
say, I welcome any feedback on this, and I may be completely off-base.
I'm calling this
