Re: [PATCH] ksm: Expose configuration via sysctl

From: Dave Hansen
Date: Tue Feb 25 2014 - 12:35:28 EST


On 02/24/2014 03:28 PM, 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.

Doesn't this essentially mean "don't use sysfs for configuration"?
Seems like at least /sys/kernel/mm/transparent_hugepage would need the
same treatment.

Couldn't we also (maybe in parallel) just teach the sysctl userspace
about sysfs? This way we don't have to do parallel sysctls and sysfs
for *EVERYTHING* in the kernel:

sysfs.kernel.mm.transparent_hugepage.enabled=enabled

Or do we just say "sysctls are the way to go for anything that might
need to be persistent, don't use sysfs"?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/