Skip to contentSkip to conversation

ksm: Expose configuration via sysctl

PATCH In review Alexander Graf 8 participants 14 messages Feb 24, 2014 – Feb 26, 2014

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 ksm: Expose configuration via sysctl

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.

---
 kernel/sysctl.c |   10 +++++++
 mm/ksm.c        |   78 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 88 insertions(+), 0 deletions(-)
kernel/sysctl.c +10 -0
index 332cefc..2169a00 100644
@@ -217,6 +217,9 @@ extern struct ctl_table random_table[];
 #ifdef CONFIG_EPOLL
 extern struct ctl_table epoll_table[];
 #endif
+#ifdef CONFIG_KSM
+extern struct ctl_table ksm_table[];
+#endif
 
 #ifdef HAVE_ARCH_PICK_MMAP_LAYOUT
 int sysctl_legacy_va_layout;
@@ -1279,6 +1282,13 @@ static struct ctl_table vm_table[] = {
 	},
 
 #endif /* CONFIG_COMPACTION */
+#ifdef CONFIG_KSM
+	{
+		.procname	= "ksm",
+		.mode		= 0555,
+		.child		= ksm_table,
+	},
+#endif
 	{
 		.procname	= "min_free_kbytes",
 		.data		= &min_free_kbytes,
mm/ksm.c +78 -0

84 lines not on this page · raw message

Signature · 7 lines
1.6.0.2

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to [email protected].  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Reviewed-by on v1 1/1
#1 lore raw
Quoted 7 lines · Alexander Graf

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.

Quoted 6 lines

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.

Signature · 7 lines
All rights reversed

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to [email protected].  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
#2 lore raw
In reply to Alexander Graf
Quoted 33 lines · Alexander Graf

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.

---
 kernel/sysctl.c |   10 +++++++
 mm/ksm.c        |   78 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 88 insertions(+), 0 deletions(-)
kernel/sysctl.c +3 -0
index 332cefc..2169a00 100644
@@ -217,6 +217,9 @@ extern struct ctl_table random_table[];
 #ifdef CONFIG_EPOLL
 extern struct ctl_table epoll_table[];
 #endif
+#ifdef CONFIG_KSM
+extern struct ctl_table ksm_table[];
+#endif
 
 #ifdef HAVE_ARCH_PICK_MMAP_LAYOUT
 int sysctl_legacy_va_layout;

kernel/sysctl.c static struct ctl_table vm_table[] = { · line 1291

Quoted 10 lines
kernel/sysctl.c +7 -0
@@ -1279,6 +1282,13 @@ static struct ctl_table vm_table[] = {
 	},
 
 #endif /* CONFIG_COMPACTION */
+#ifdef CONFIG_KSM
+	{
+		.procname	= "ksm",
+		.mode		= 0555,
+		.child		= ksm_table,
+	},
+#endif

ksm can be a module, so this won't work.

Can we make those controls proper module parameters instead?

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>

#3 lore raw
Quoted 47 lines · Johannes Weiner
Quoted 33 lines · Alexander Graf

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.

---
 kernel/sysctl.c |   10 +++++++
 mm/ksm.c        |   78 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 88 insertions(+), 0 deletions(-)
kernel/sysctl.c +3 -0
index 332cefc..2169a00 100644
@@ -217,6 +217,9 @@ extern struct ctl_table random_table[];
 #ifdef CONFIG_EPOLL
 extern struct ctl_table epoll_table[];
 #endif
+#ifdef CONFIG_KSM
+extern struct ctl_table ksm_table[];
+#endif
 
 #ifdef HAVE_ARCH_PICK_MMAP_LAYOUT
 int sysctl_legacy_va_layout;

kernel/sysctl.c static struct ctl_table vm_table[] = { · line 1291

Quoted 10 lines
kernel/sysctl.c +7 -0
@@ -1279,6 +1282,13 @@ static struct ctl_table vm_table[] = {
 	},
 
 #endif /* CONFIG_COMPACTION */
+#ifdef CONFIG_KSM
+	{
+		.procname	= "ksm",
+		.mode		= 0555,
+		.child		= ksm_table,
+	},
+#endif

ksm can be a module, so this won't work.

Quoted 1 line

Can we make those controls proper module parameters instead?

You can do dynamic sysctl registration and removal. Its its own little filesystem of sorts.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>

#4 lore raw
Quoted 52 lines
Quoted 52 lines

Am 26.02.2014 um 01:19 schrieb Peter Zijlstra <[email protected]>:

Quoted 35 lines · Johannes Weiner

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.

---

kernel/sysctl.c |   10 +++++++
mm/ksm.c        |   78 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 88 insertions(+), 0 deletions(-)
kernel/sysctl.c +3 -0
index 332cefc..2169a00 100644
@@ -217,6 +217,9 @@ extern struct ctl_table random_table[];
 #ifdef CONFIG_EPOLL
 extern struct ctl_table epoll_table[];
 #endif
+#ifdef CONFIG_KSM
+extern struct ctl_table ksm_table[];
+#endif
 
 #ifdef HAVE_ARCH_PICK_MMAP_LAYOUT
 int sysctl_legacy_va_layout;

kernel/sysctl.c static struct ctl_table vm_table[] = { · line 1291

Quoted 10 lines
kernel/sysctl.c +7 -0
@@ -1279,6 +1282,13 @@ static struct ctl_table vm_table[] = {
  },
 
 #endif /* CONFIG_COMPACTION */
+#ifdef CONFIG_KSM
+    {
+        .procname    = "ksm",
+        .mode        = 0555,
+        .child        = ksm_table,
+    },
+#endif

ksm can be a module, so this won't work.

Quoted 4 lines
Quoted 1 line

Can we make those controls proper module parameters instead?

You can do dynamic sysctl registration and removal. Its its own little filesystem of sorts.

Hm. Doesn't this open another big can of worms? If we have ksm as a module and our sysctl helpers try to enable ksm on boot, they may not be able to because the module hasn't been loaded yet.

So in that case, we want to always register the sysctl and dynamically load the ksm module when the sysctl gets accessed - similar to how we can do stub devices that load modiles, no?

Alex
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>

#5 lore raw
Quoted 52 lines · Alexander Graf
Quoted 52 lines
Quoted 52 lines

Am 26.02.2014 um 01:19 schrieb Peter Zijlstra <[email protected]>:

Quoted 35 lines · Johannes Weiner

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.

---

kernel/sysctl.c |   10 +++++++
mm/ksm.c        |   78 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 88 insertions(+), 0 deletions(-)
kernel/sysctl.c +3 -0
index 332cefc..2169a00 100644
@@ -217,6 +217,9 @@ extern struct ctl_table random_table[];
 #ifdef CONFIG_EPOLL
 extern struct ctl_table epoll_table[];
 #endif
+#ifdef CONFIG_KSM
+extern struct ctl_table ksm_table[];
+#endif
 
 #ifdef HAVE_ARCH_PICK_MMAP_LAYOUT
 int sysctl_legacy_va_layout;

kernel/sysctl.c static struct ctl_table vm_table[] = { · line 1291

Quoted 10 lines
kernel/sysctl.c +7 -0
@@ -1279,6 +1282,13 @@ static struct ctl_table vm_table[] = {
  },
 
 #endif /* CONFIG_COMPACTION */
+#ifdef CONFIG_KSM
+    {
+        .procname    = "ksm",
+        .mode        = 0555,
+        .child        = ksm_table,
+    },
+#endif

ksm can be a module, so this won't work.

Quoted 8 lines
Quoted 4 lines
Quoted 1 line

Can we make those controls proper module parameters instead?

You can do dynamic sysctl registration and removal. Its its own little filesystem of sorts.

Hm. Doesn't this open another big can of worms? If we have ksm as a module and our sysctl helpers try to enable ksm on boot, they may not be able to because the module hasn't been loaded yet.

So in that case, we want to always register the sysctl and dynamically load the ksm module when the sysctl gets accessed - similar to how we can do stub devices that load modiles, no?

The files sysctl tries to write to at bootup need to be all there right from the start, otherwise there can't be anything to access, and no way to trigger any module load.

The auto-load stuff in /dev works by userspace creating dead device nodes with the proper dev_t before the device exists, which is a very different model.

sysctl is not suitable for any instantiated or conditional data like loadable module, devices, ... Things need to be there right from the start, later registered facilities will not be noticed by sysctl in userspace and are therefore not hooked into system management. If any values should be applied from userspace, this will not really work out.

There a network devices configs doing that today, and they don't really work that well; it's a gigantic stupid hack in userspace to fiddle with /proc/sys/ when a netdev shows up, no model to copy to any new facility.

Usually, loadable module parameter need to live in /sys/module/ or /sys/bus/, where uevents are generated and udev can pick up the event and apply system configuration.

Kay

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>

#6 lore raw
In reply to Johannes Weiner
Quoted 5 lines · Johannes Weiner
Quoted 4 lines · Alexander Graf

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).

Quoted 8 lines
Quoted 6 lines

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?

I don't mind Alex's patch, but I do think the same should be done for THP as for KSM, and a general solution more attractive than more #ifdefs one by one. Should a general solution just be in userspace, in sysctl(8)?

Hugh

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>

#7 lore raw
Quoted 13 lines

Am 26.02.2014 um 09:05 schrieb Hugh Dickins <[email protected]>:

Quoted 9 lines · Johannes Weiner
Quoted 8 lines · Alexander Graf

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.

Quoted 8 lines
Quoted 5 lines
Quoted 3 lines

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.

Quoted 3 lines

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.

Quoted 2 lines

solution more attractive than more #ifdefs
one by one. Should a general

I don't see a good alternative to this.

Quoted 1 line

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, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>

#8 lore raw
In reply to Alexander Graf
Quoted 10 lines · Alexander Graf

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"?

#9 lore raw
Quoted 20 lines

Am 26.02.2014 um 01:34 schrieb Dave Hansen <[email protected]>:

Quoted 11 lines · Alexander Graf

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.

Quoted 5 lines

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

It's pretty hard to filter this. We definitely do not want to expose all of sysfs through /proc/sys. But how do we know which files are actual configuration and which ones are dynamic system introspection data?

We could add a filter, but then we can just as well stick with the manual approach I followed here :).

Quoted 3 lines

Or do we just say "sysctls are the way to go for anything that might need to be persistent, don't use sysfs"?

IMHO there are 2 paths we can take:

1) Admit that using sysfs for configuration is a bad idea, use sysctl instead

2) Invent a streamlined way to set sysfs configuration variables similar to how we can set sysctl values

I'm not really sure which path is nicer. But the sitaution today is not exactly satisfactory. The most common solution to ksm configuration is an init or systemd script that sets the respective config variables.

Alex
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>

#10 lore raw
Quoted 9 lines · Alexander Graf
Quoted 5 lines

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

It's pretty hard to filter this. We definitely do not want to expose all of sysfs through /proc/sys. But how do we know which files are actual configuration and which ones are dynamic system introspection data?

We could add a filter, but then we can just as well stick with the manual approach I followed here :).

Maybe not stick it under /proc/sys, but teach sysctl(8) about them. I guess at the moment, sysctl says that it's tied to /proc/sys:

Quoted 3 lines

DESCRIPTION
sysctl is used to modify kernel parameters at runtime. The parameters available are those listed under /proc/sys/. Procfs is required for sysctl support in Linux. You can use sysctl to both read and write sysctl data.

But surely that's not set in stone just because the manpage says so. :)

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>

#11 lore raw
Quoted 11 lines · Dave Hansen
Quoted 9 lines · Alexander Graf
Quoted 5 lines

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

It's pretty hard to filter this. We definitely do not want to expose all of sysfs through /proc/sys. But how do we know which files are actual configuration and which ones are dynamic system introspection data?

We could add a filter, but then we can just as well stick with the manual approach I followed here :).

Quoted 8 lines

Maybe not stick it under /proc/sys, but teach sysctl(8) about them. I guess at the moment, sysctl says that it's tied to /proc/sys:

Quoted 3 lines

DESCRIPTION
sysctl is used to modify kernel parameters at runtime. The parameters available are those listed under /proc/sys/. Procfs is required for sysctl support in Linux. You can use sysctl to both read and write sysctl data.

But surely that's not set in stone just because the manpage says so. :)

What I still don't get is why you need this?

My distribution (Debian) has a sysfsutils package which provides a /etc/sysfs.conf / /etc/sysfs.d/foo exactly like /etc/sysctl.conf.

Don't other distributions have something like this?

c'ya
sven-haegar

Signature · 8 lines
Three may keep a secret, if two of them are dead.
- Ben F.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to [email protected].  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
#12 lore raw
Quoted 26 lines · Sven-Haegar Koch
Quoted 16 lines · Dave Hansen
Quoted 10 lines · Alexander Graf
Quoted 6 lines

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

It's pretty hard to filter this. We definitely do not want to expose all of sysfs through /proc/sys. But how do we know which files are actual configuration and which ones are dynamic system introspection data?

We could add a filter, but then we can just as well stick with the manual approach I followed here :).

Maybe not stick it under /proc/sys, but teach sysctl(8) about them. I guess at the moment, sysctl says that it's tied to /proc/sys:

Quoted 6 lines
Quoted 4 lines

DESCRIPTION
sysctl is used to modify kernel parameters at runtime. The parameters available are those listed under /proc/sys/. Procfs is required for sysctl support in Linux. You can use sysctl to both read and write sysctl data.

But surely that's not set in stone just because the manpage says so. :)

Quoted 7 lines

What I still don't get is why you need this?

My distribution (Debian) has a sysfsutils package which provides a /etc/sysfs.conf / /etc/sysfs.d/foo exactly like /etc/sysctl.conf.

Don't other distributions have something like this?

Maybe that's the right answer to the problem, but I still don't understand why these properties were put into sysfs in the first place. We're not configuring a dynamic device here, are we?

Also if we do want something like a sysfs.conf and sysfs.d, that should probably be something that gets properly coordinated between distributions so that users don't get completely confused. Today openSUSE does not have a sysfs.conf/.d provided by the sysfsutils package. Maybe it's something homegrown?

Alex

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>

#13 lore raw
In reply to Dave Hansen
Quoted 16 lines · Dave Hansen
Quoted 10 lines · Alexander Graf

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.

Quoted 8 lines

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"?

Support in sysctl for setting static data in /sys might make sense for some rare use cases.

It's still not obvious how to handle the dynamic nature of most of the data that is created by modules, and which data belongs into udev rules and which in the "sysctl /sys" settings.

Kay

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>