lkml.org 
[lkml]   [2023]   [Jan]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v13 3/6] mm/vmstat: manage per-CPU stats from CPU context when NOHZ full
Hi Hillf,

On Sat, Jan 07, 2023 at 08:15:29AM +0800, Hillf Danton wrote:
> On 6 Jan 2023 15:16:23 -0300 Marcelo Tosatti <mtosatti@redhat.com>
> > On Fri, Jan 06, 2023 at 11:01:54PM +0800, Hillf Danton wrote:
> > > On 6 Jan 2023 09:51:00 -0300 Marcelo Tosatti <mtosatti@redhat.com>
> > > > On Fri, Jan 06, 2023 at 08:12:44AM +0800, Hillf Danton wrote:
> > > > >
> > > > > Regression wrt V12 if timer is added on the CPU that is not doing HK_TYPE_TIMER?
> > > >
> > > > Before this change, the timer was managed (and queued on an isolated
> > > > CPU) by vmstat_shepherd. Now it is managed (and queued) by the local
> > > > CPU, so there is no regression.
> > >
> > > Given vm stats folded when returning to userspace, queuing the delayed work
> > > barely makes sense in the first place. If it can be canceled, queuing it burns
> > > cycles with nothing earned. Otherwise vm stats got folded already.
> >
> > Agree, but you can't know whether return to userspace will occur
> > before the timer is fired.
>
> No way to predict a random timer expiration, no?

Right.

> >
> > So queueing the timer is to _ensure_ that eventually vmstats will be
> > synced (which maintains the current timing behaviour wrt vmstat syncs).
>
> After this change,
>
> > > > > > @@ -1988,13 +2022,19 @@ void quiet_vmstat(void)
> > > > > > if (!is_vmstat_dirty())
> > > > > > return;
> > > > > >
>
> it is only ensured eventually by this check instead.

Yes, but if you do not return to userspace, then the per-CPU vm
statistics can be dirty indefinitely.

> > > > > > + refresh_cpu_vm_stats(false);
> > > > > > +
> > > > > > + if (!IS_ENABLED(CONFIG_FLUSH_WORK_ON_RESUME_USER))
> > > > > > + return;
> > > > > > +
> > > > > > + if (!user)
> > > > > > + return;
>
>
> > Also don't think the queueing cost is significant: it only happens
> > for the first vmstat dirty item.
>
> Cost is considered only if it is needed.

Not sure i understand what you mean (or whether there is any alternative
to the timer).

\
 
 \ /
  Last update: 2023-03-26 23:33    [W:0.443 / U:0.012 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site