On Tue, Apr 23, 2019 at 03:04:16PM -0700, Suren Baghdasaryan wrote: > On Tue, Apr 23, 2019 at 11:58 AM Luigi Semenzato <semenzato@xxxxxxxxxx> wrote: > > The chrome browser is a multi-process app and there is a lot of IPC. When > > process A is blocked on memory allocation, it cannot respond to IPC > > from process B, thus effectively both processes are blocked on > > allocation, but we don't see that. > > I don't think PSI would account such an indirect stall when A is > waiting for B and B is blocked on memory access. B's stall will be > accounted for but I don't think A's blocked time will go into PSI > calculations. The process inter-dependencies are probably out of scope > for PSI. Well, yes and no. We don't do explicit dependency tracking, but when A is waiting on B it's also not considered productive, so it doesn't factor into the equation. psi will see B blocked on memory and no other productive processes, which means FULL state until B resumes.
