> >>
> >> What we would need (as a start) to handle all of this with memcg would be 
> >> to accounted the resources to the process which referenced it and not the 
> >> one which allocated it.
> >
> > Irrespective of memcg charging decision, one of my request would be to at 
> > least
> > have global counters for the GPU memory which this series is adding. That 
> > would
> > be very similar to NR_KERNEL_FILE_PAGES where we explicit opt-out of memcg
> > charging but keep the global counter, so the admin can identify the reasons
> > behind high unaccounted memory on the system.
>
> Sounds reasonable to me. I will try to give this set another review round.

I think I will try and land the first 6 patches in this series soon,
this adds the basic counters, and ports the pool to use list_lru, so
drops a bunch of TTM specific code in favour of core kernel code,

They also don't create any uapi, it's just two counters to expose in
the VM stats that the GPU is using that memory.

Dave.

Reply via email to