For this case we could probably fix it without any real performance impact if we actually prioritized it.
Put 14 more bits for a counter in each row, and adjust the DDR interface semantics to guarantee time for the extra refreshes, and I think you avoid all the problems this attack depends on.
Total cost <0.1%
Don't cheap out with a tiny hash table stuck to the side or whatnot.
Put 14 more bits for a counter in each row, and adjust the DDR interface semantics to guarantee time for the extra refreshes, and I think you avoid all the problems this attack depends on.
Total cost <0.1%
Don't cheap out with a tiny hash table stuck to the side or whatnot.