On Fri, May 20, 2022 at 12:29 AM Michal Hocko <mhocko@xxxxxxxx> wrote: > > On Fri 20-05-22 10:45:43, Vaibhav Jain wrote: > > > > Thanks for looking into this patch Michal, > > > > Michal Hocko <mhocko@xxxxxxxx> writes: > > > > > On Thu 19-05-22 04:08:15, Vaibhav Jain wrote: > > >> [1] Provides a way for user-space to trigger proactive reclaim by introducing > > >> a write-only memcg file 'memory.reclaim'. However reclaim stats like number > > >> of pages scanned and reclaimed is still not directly available to the > > >> user-space. > > >> > > >> This patch proposes to extend [1] to make the memcg file 'memory.reclaim' > > >> readable which returns the number of pages scanned / reclaimed during the > > >> reclaim process from 'struct vmpressure' associated with each memcg. This should > > >> let user-space asses how successful proactive reclaim triggered from memcg > > >> 'memory.reclaim' was ? > > >> > > >> With the patch following command flow is expected: > > >> > > >> # echo "1M" > memory.reclaim > > >> > > >> # cat memory.reclaim > > >> scanned 76 > > >> reclaimed 32 > > > > > > Why cannot you use memory.stat? Sure it would require to iterate over > > > the reclaimed hierarchy but the information about scanned and reclaimed > > > pages as well as other potentially useful stats is there. > > > > Agree that "memory.stat" is more suitable for scanned/reclaimed stats as > > it already is exposing bunch of other stats. > > > > The discussion on this patch however seems to have split into two parts: > > > > 1. Is it a good idea to expose nr_scanned/nr_reclaimed to users-space > > and if yes how ? > > > > IMHO, I think it will be better to expose this info via 'memory.stat' as it > > can be useful insight into the reclaim efficiency and vmpressure. > > We already do that with some more metrics > pgrefill 9801926 > pgscan 27329762 > pgsteal 22715987 > pgactivate 250691267 > pgdeactivate 9521843 > pglazyfree 0 > pglazyfreed 0 > > > 2. Will it be useful to provide feedback to userspace when it writes to > > 'memory.reclaim' on how much memory has been reclaimed ? > > > > IMHO, this will be a useful feeback to userspace to better adjust future > > proactive reclaim requests via 'memory.reclaim' > > How precise this information should be? A very simplistic approach would > be > cp memory.stat stats.before > echo $WHATEVER > memory.reclaim > cp memory.stat stats.after > > This will obviously contain also activity outside of the explicitly > triggered reclaim (racing background/direct reclaim) but isn't that what > actually matters? Are there any cases where the only metric you care > about is the triggered reclaim in isolation? I think it might be useful to have a dedicated entry in memory.stat for proactively reclaimed memory. A case where this would be useful is tuning and evaluating userspace proactive reclaimers. For instance, if a userspace agent is asking the kernel to reclaim 100M, but it could only reclaim 10M, then most probably the proactive reclaimer is not using a good methodology to figure out how much memory do we need to reclaim. IMO this is more useful, and a superset of just reading the last reclaim request status through memory.reclaim (read stat before and after). Additionally, things get complicated if the userspace agent is multi-threaded. For a cumulative entry in memory.stat, it shouldn't matter by a lot as we are looking at the total for all threads cumulatively anyway. If we are only reading the memory reclaimed in the last request (through memory.reclaim), then we can easily get the results of a request that happened on a different thread. > > -- > Michal Hocko > SUSE Labs
