> So, if we go and apply your logic to a 1GB system we should resize the > vmalloc area to 0 bytes in order to avoid RAM truncation without > CONFIG_HIGHMEM?
As you already know, CONFIG_HIGHMEM option is necessary if RAM is more than 1GB. So no need to resize vmalloc area to 0. > Sorry, but the only sane options here are to either live with the > truncation, enable CONFIG_HIGHMEM, or set vmalloc size manually. > Changing a default value that affects everyone for the benefit of your > specific use-case isn't a sane option. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
