On Tue 17-09-19 05:06:46, Matthew Wilcox wrote: > On Tue, Sep 17, 2019 at 07:58:24PM +0800, Lin Feng wrote: [...] > > +mm_reclaim_congestion_wait_jiffies > > +========== > > + > > +This control is used to define how long kernel will wait/sleep while > > +system memory is under pressure and memroy reclaim is relatively active. > > +Lower values will decrease the kernel wait/sleep time. > > + > > +It's suggested to lower this value on high-end box that system is under memory > > +pressure but with low storage IO utils and high CPU iowait, which could also > > +potentially decrease user application response time in this case. > > + > > +Keep this control as it were if your box are not above case. > > + > > +The default value is HZ/10, which is of equal value to 100ms independ of how > > +many HZ is defined. > > Adding a new tunable is not the right solution. The right way is > to make Linux auto-tune itself to avoid the problem. I absolutely agree here. From you changelog it is also not clear what is the underlying problem. Both congestion_wait and wait_iff_congested should wake up early if the congestion is handled. Is this not the case? Why? Are you sure a shorter timeout is not just going to cause problems elsewhere. These sleeps are used to throttle the reclaim. I do agree there is no great deal of design behind them so they are more of "let's hope it works" kinda thing but making their timeout configurable just doesn't solve this at all. You are effectively exporting a very subtle implementation detail into the userspace. -- Michal Hocko SUSE Labs
