On Mon, Mar 1, 2021 at 5:16 PM Roman Gushchin <guro@xxxxxx> wrote: > > On Mon, Mar 01, 2021 at 02:22:26PM +0800, Muchun Song wrote: > > The remote memcg charing APIs is a mechanism to charge kernel memory > > to a given memcg. So we can move the infrastructure to the scope of > > the CONFIG_MEMCG_KMEM. > > This is not a good idea, because there is nothing kmem-specific > in the idea of remote charging, and we definitely will see cases > when user memory is charged to the process different from the current. > Indeed and which remind me: what happened to the "Charge loop device i/o to issuing cgroup" series? That series was doing remote charging for user pages.
