Re: kern/55166: uvm_pdpolicy_clock params (anon/exec/file max/min)defaults

[Izumi Tsutsui <tsutsui%ceres.dti.ne.jp@localhost>]

The following reply was made to PR kern/55166; it has been noted by GNATS.

From: Izumi Tsutsui <tsutsui%ceres.dti.ne.jp@localhost>
To: mrg%eterna.com.au@localhost
Cc: gnats-bugs%netbsd.org@localhost, tsutsui%ceres.dti.ne.jp@localhost
Subject: Re: kern/55166: uvm_pdpolicy_clock params (anon/exec/file max/min)defaults
Date: Tue, 14 Apr 2020 00:23:57 +0900

 mrg@ wrote:
 
 > >  Are you suggesting existing CLOCK_INACTIVEPCT should also be changed?
 > >  (maybe it's okay because it is not mentioned in options(4) though)
 > >  
 > >  Note these parameters are also in sysctl(9) but without "pdpolicy_clock":
 > >  ---
 > >  % sysctl vm
 > >   :
 > >  vm.anonmin = 10
 > >  vm.filemin = 5
 > >  vm.execmin = 30
 > >  vm.anonmax = 60
 > >  vm.filemax = 20
 > >  vm.execmax = 50
 > >  vm.inactivepct = 33
 > 
 > yes - these values are initialised by clock as well as clockpro.
 > 
 > i think i general PDPOLICY_<value> seems better for now, with
 > out the CLOCK in the name, but with PDPOLICY in the name.
 
 In clockpro, anon/file/exec min/max parameters are not implemented.
 Should it be eventually fixed, as noted in PR/35741?
  https://gnats.netbsd.org/35741
 
 If so PDPOLICY_ANONMAX etc. seems fine for me.
 (but I'll leave existing CLOCK_INACTIVEPCT as is)
 
 ---
 Izumi Tsutsui