Le 22/02/2018 à 21:14, Maxime Villard a écrit :
Hi,
I intend to enable SVS by default soon.
[...]
I've enabled it.
Maxime
In article <79261937-8dc1-aeb6-ebd4-c4dcb4027...@m00nbsd.net>,
Maxime Villard wrote:
>Le 23/02/2018 à 10:45, Edgar Fuà a écrit :
>> MV> A sysctl is now available, machdep.svs_enabled
>> EF> Why svs_enabled and not simply svs?
>> MV> Because that's the common naming
Le 23/02/2018 à 10:45, Edgar Fuß a écrit :
MV> A sysctl is now available, machdep.svs_enabled
EF> Why svs_enabled and not simply svs?
MV> Because that's the common naming convention? The name of the sysctl entry
MV> matches the name of the associated kernel variable.
What I meant is:
$ sysctl -a
MV> A sysctl is now available, machdep.svs_enabled
EF> Why svs_enabled and not simply svs?
MV> Because that's the common naming convention? The name of the sysctl entry
MV> matches the name of the associated kernel variable.
What I meant is:
$ sysctl -a | grep -F _enable | wc -l
0
$ sysctl
Le 22/02/2018 à 21:53, Edgar Fuß a écrit :
A sysctl is now available, machdep.svs_enabled
Why svs_enabled and not simply svs?
Because that's the common naming convention? The name of the sysctl entry
matches the name of the associated kernel variable.
In case you intend to add more
> A sysctl is now available, machdep.svs_enabled
Why svs_enabled and not simply svs?
In case you intend to add more svs-related sysctls in the future, prior art
seems to suggest svs.enable(d), not svs_enabled.
Hi,
I intend to enable SVS by default soon. This will be done by uncommenting this
line in GENERIC:
#optionsSVS # Separate Virtual Space
When SVS is compiled, it is automatically turned off at boot time if the CPU
vendor is not Intel. That is to say, if you use AMD,