From: Vasily Averin <vvs-5HdwGun5lf+gSpxsJD1C4w@public.gmane.org>
To: Michal Hocko <mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>,
Vladimir Davydov
<vdavydov.dev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
Cgroups <cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux MM <linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
kernel-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org
Subject: memcg memory accounting in vmalloc is broken
Date: Thu, 7 Oct 2021 11:04:40 +0300 [thread overview]
Message-ID: <b3c232ff-d9dc-4304-629f-22cc95df1e2e@virtuozzo.com> (raw)
vmalloc was switched to __alloc_pages_bulk but it does not account the memory to memcg.
Is it known issue perhaps?
thank you,
Vasily Averin
next reply other threads:[~2021-10-07 8:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 8:04 Vasily Averin [this message]
[not found] ` <b3c232ff-d9dc-4304-629f-22cc95df1e2e-5HdwGun5lf+gSpxsJD1C4w@public.gmane.org>
2021-10-07 8:13 ` memcg memory accounting in vmalloc is broken Michal Hocko
[not found] ` <YV6sIz5UjfbhRyHN-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2021-10-07 8:16 ` Michal Hocko
[not found] ` <YV6s+ze8LzuxfvOM-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2021-10-07 8:50 ` Vasily Averin
[not found] ` <953ef8e2-1221-a12c-8f71-e34e477a52e8-5HdwGun5lf+gSpxsJD1C4w@public.gmane.org>
2021-10-07 10:08 ` Michal Hocko
2021-10-07 14:00 ` Vlastimil Babka
[not found] ` <0668b6d8-6f8c-07c7-75e0-5448ea87cb54-AlSwsSmVLrQ@public.gmane.org>
2021-10-07 14:09 ` Michal Hocko
2021-10-07 19:33 ` Vasily Averin
[not found] ` <6411d3f7-b3a4-23a8-14fc-fcf6b9c5b73a-5HdwGun5lf+gSpxsJD1C4w@public.gmane.org>
2021-10-08 9:23 ` [PATCH memcg] memcg: enable memory accounting in __alloc_pages_bulk Vasily Averin
[not found] ` <bf3b1364-2c48-533f-9dae-22470074a037-5HdwGun5lf+gSpxsJD1C4w@public.gmane.org>
2021-10-08 17:35 ` Shakeel Butt
[not found] ` <CALvZod7_fhgV39HXmmMApubW-39CjJ5t+WjmkyA_DNGF7b5O+w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-10-12 10:18 ` [PATCH mm v2] " Vasily Averin
[not found] ` <2410e99a-087c-3f89-9bdf-b62a7d5df725-5HdwGun5lf+gSpxsJD1C4w@public.gmane.org>
2021-10-12 13:10 ` Mel Gorman
[not found] ` <20211012131019.GV3959-3eNAlZScCAx27rWaFMvyedHuzzzSOjJt@public.gmane.org>
2021-10-12 13:40 ` Vasily Averin
[not found] ` <0baa2b26-a41b-acab-b75d-72ec241f5151-5HdwGun5lf+gSpxsJD1C4w@public.gmane.org>
2021-10-12 14:58 ` [PATCH mm v3] " Vasily Averin
[not found] ` <60df0efd-f458-a13c-7c89-749bdab21d1d-5HdwGun5lf+gSpxsJD1C4w@public.gmane.org>
2021-10-12 15:19 ` Shakeel Butt
2021-10-12 15:20 ` Mel Gorman
2021-10-12 15:36 ` Michal Hocko
[not found] ` <YWWrai/ChIgycgCo-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2021-10-12 16:08 ` Shakeel Butt
[not found] ` <CALvZod7LpEY98r=pD-k=WbOT-z=Ux16Mfmv3s7PDtJg6=ZStgw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-10-12 18:24 ` Michal Hocko
[not found] ` <YWXS09ZBhZSy6FQQ-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2021-10-13 16:41 ` Shakeel Butt
[not found] ` <CALvZod6K6UXxDrkHp=mVDV7O-fAtmRkgMDngPazBhcyDUNxy_Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-10-13 17:16 ` Michal Hocko
[not found] ` <YWcUbXfBsbNzYIad-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2021-10-13 17:30 ` Shakeel Butt
2021-10-12 18:45 ` Vasily Averin
2021-10-14 8:02 ` [PATCH mm v5] " Vasily Averin
[not found] ` <65c1afaf-7947-ce28-55b7-06bde7aeb278-5HdwGun5lf+gSpxsJD1C4w@public.gmane.org>
2021-10-15 21:34 ` Andrew Morton
2021-10-16 6:04 ` Vasily Averin
2021-10-07 10:20 ` memcg memory accounting in vmalloc is broken Mel Gorman
[not found] ` <20211007102044.GR3959-3eNAlZScCAx27rWaFMvyedHuzzzSOjJt@public.gmane.org>
2021-10-07 14:02 ` Vlastimil Babka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b3c232ff-d9dc-4304-629f-22cc95df1e2e@virtuozzo.com \
--to=vvs-5hdwgun5lf+gspxsjd1c4w@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
--cc=kernel-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=vdavydov.dev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox