于 2011年06月22日 11:29, David Rientjes 写道:
Either way, this patch isn't needed since it has no benefit over doing it through an init script.
If you were right, CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS is not needed, you can do it through an init script. If you were right, the 512M limit is not needed neither, you have transparent_hugepage=never boot parameter and do the check of 512M later in an init script. (Actually, moving the 512M check to user-space is really more sane to me.) I am quite sure you have lots of other things which both have a Kconfig and a boot parameter, why do we have it? -- 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>