On Thu, Sep 03, 2015 at 10:34:32AM +0200, Lucas Stach wrote: > Am Donnerstag, den 03.09.2015, 17:28 +0900 schrieb Yongtaek Lee: > > As i know "vmalloc=size" is not mandatory so that i think default value of > > vmalloc_min is wrong. > > > 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? > > 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.
Exactly right. -- FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net. -- 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/