> Am 26.02.2014 um 09:05 schrieb Hugh Dickins <hu...@google.com>: > >> On Tue, 25 Feb 2014, Johannes Weiner wrote: >>> On Tue, Feb 25, 2014 at 12:28:04AM +0100, Alexander Graf wrote: >>> Configuration of tunables and Linux virtual memory settings has >>> traditionally >>> happened via sysctl. Thanks to that there are well established ways to make >>> sysctl configuration bits persistent (sysctl.conf). >>> >>> KSM introduced a sysfs based configuration path which is not covered by user >>> space persistent configuration frameworks. >>> >>> In order to make life easy for sysadmins, this patch adds all access to all >>> KSM tunables via sysctl as well. That way sysctl.conf works for KSM as well, >>> giving us a streamlined way to make KSM configuration persistent. >> >> ksm can be a module, so this won't work. > > That's news to me. Are you writing of some Red Hat patches, or just > misled by the "module_init(ksm_init)" which used the last line of ksm.c?
Ugh, sorry. I should have double-checked this. KSM is bool in Kconfig and so is THP. > > I don't mind Alex's patch, but I do think the same should be done for > THP as for KSM, and a general I agree. > solution more attractive than more #ifdefs > one by one. Should a general I don't see a good alternative to this. > solution just be in userspace, in sysctl(8)? User space needs to have the ability to list available sysctls, so we need to have an enumerable map between sys and sysctl somewhere. Keeping that list close to where the actual files are implemented seems to make sense to me, as it's very hard to miss out on addition and removal of parameters throughout the stack this way. That's why I put it here. Alex -- 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/
