Chester (lamchester.delete@this.gmail.com) on January 7, 2021 8:14 pm wrote:
> > How is that going to help? Refreshing the memory will just
> > "refresh" the flipped bits and you won't know a thing.
>
> No, not software refresh. I'm talking about refreshing the charge in DRAM cell capacitors.
> Rowhammer can happen because accessing adjacent cells can cause a cell's charge to leak faster.
> If enough of it leaks before a charge refresh, you get a bit flip. Read https://arxiv.org/pdf/1904.09724.pdf
> for more details, in the 'Rowhammer Mechanisms' section.

I wasn't talking about software refresh, but well put and point taken which I presume to be that it takes less to flip bit when the capacitor supporting it is nearly exhausted. So, I stand corrected at least in part.

> > Currently some RAM manufactures are offering LPDDR4 modules with on-board ECC and from
> > what I've seen it is mandatory for DDR5/LPDDR5. The intent of ECC in these instances
> > is not to increase overall memory reliability/resiliency but to enable reduced power
> > consumption partly through lessened refresh rates. Back to square one. Sheesh!
>
> I think that's asking for trouble.
>
> By the way, DRAM manufacturers have also tried targeted row refresh in hopes of mitigating rowhammer without
> tightening global refresh timings. But researchers have figured out ways past that too. Depending on the
> specific implementation of targeted row refresh, you can sometimes cause bit flips by hammering more rows.

Asking for trouble indeed. I'm incensed how brazenly the big pictures is being lost at the expense of customers, users and society as a whole. Using error correction to reduce fundamental resiliency rather than building reliability on top of it.