Re: [PATCH v2 0/3] support for broken memory modules (BadRAM)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 06/22/2011 12:01 PM, Nancy Yuen wrote:
> 
> Good point.  There's the MAX_NODES that expands it, though it's still
> hard coded, and as I understand, intended for NUMA node entries.  We
> need anywhere from 8K to 64K 'bad' entries.  This creates holes and
> translates to twice as many entries in the e820.  We only want to
> allow this memory if it's needed, instead of hard coding it.
> 

It should be dynamic, probably.  We can waste memory during early
reclaim, but the memblock stuff should be dynamic.

	-hpa

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>


[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]