Re: [PATCH v7 00/13] fold per-CPU vmstats remotely

Frederic Weisbecker
2023-04-19T12:24:21Z

Le Wed, Apr 19, 2023 at 08:59:28AM -0300, Marcelo Tosatti a écrit :
> On Wed, Apr 19, 2023 at 08:29:47AM -0300, Marcelo Tosatti wrote:
> > On Wed, Apr 19, 2023 at 08:14:09AM -0300, Marcelo Tosatti wrote:
> > > This was tried before:
> > > https://lore.kernel.org/lkml/20220127173037.318440631@fedora.localdomain/
> > >
> > > My conclusion from that discussion (and work) is that a special system
> > > call:
> > >
> > > 1) Does not allow the benefits to be widely applied (only modified
> > > applications will benefit). Is not portable across different operating systems.
> > >
> > > Removing the vmstat_work interruption is a benefit for HPC workloads,
> > > for example (in fact, it is a benefit for any kind of application,
> > > since the interruption causes cache misses).
> > >
> > > 2) Increases the system call cost for applications which would use
> > > the interface.
> > >
> > > So avoiding the vmstat_update update interruption, without userspace
> > > knowledge and modifications, is a better than solution than a modified
> > > userspace.
> >
> > Another important point is this: if an application dirties
> > its own per-CPU vmstat cache, while performing a system call,
>
> Or while handling a VM-exit from a vCPU.
>
> This are, in my mind, sufficient reasons to discard the "flush per-cpu
> caches" idea. This is also why i chose to abandon the prctrl interface
> patchset.

If you're running your isolated workloads on guests, which sounds quite
challenging but I guess you guys managed, I'd expect that VMEXITs are
absolutely out of question while the task runs critical code, so I'm not
sure why you would care. I guess not only your guests but also your hosts
run nohz_full, right?

I can't tell if the prctl solution which quiesces everything is the solution
for you, I don't know well enough your workloads, but I would expect that
the pattern is as follows:

1) Arrange for full isolation (no more interrupts/exceptions/VMEXITs)
2) Run critical code
3) Optionally do something once you're done

If vmstat is going to be the only thing to wait for on 1), then the remote
solution looks good enough (although I leave that to -mm guys as I'm too
clueless about those matters), if there is more to be expected, I guess the
quiescing prctl (or whatever syscall) is something to consider.

Thanks.