Hacker News new | past | comments | ask | show | jobs | submit login

Having physical memory segments be different logical sizes at runtime depending on the ECC setting does not sound fun.

Having your system’s available memory fluctuate up and down based on how many segments are currently set to ECC also doesn’t sound fun.

Having developers manually turn ECC off for regions where it’s unimportant sounds like a lot of complexity for a relatively rare use case.

There is in-band ECC in some newer Intel designs, but it’s all or nothing. Adding extremely complexity to memory management to selectively disable it sounds like a lot to ask.




I believe it would just be a kernel setting. Developers would just see full capacity or ecc-capacity, they wouldn’t care much why.


It’s implemented as a BIOS setting where it’s supported.

But the parent comment was suggesting that it be on or off depending on the memory segment, which is a completely different problem.


I don't see "segment" in the earlier post at all.

I think your reading depends on thinking "application" means "process", while another reading would be that an application is a particular deployed system, where this setting can be altered e.g. at the BIOS level.


Sorry yes I did mean application as in a deployed system rather than a specific process.


likewise, I assumed it was a hard system-wide setting and not application specific.




Consider applying for YC's W25 batch! Applications are open till Nov 12.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: