From: Michal Hocko <mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Zefan Li <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Cc: Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>,
Vladimir Davydov
<vdavydov.dev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Cgroups <cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Subject: Re: [PATCH] memcg: Fix memcg_kmem_bypass() for remote memcg charging
Date: Wed, 13 May 2020 13:29:05 +0200 [thread overview]
Message-ID: <20200513112905.GX29153@dhcp22.suse.cz> (raw)
In-Reply-To: <76f71776-d049-7407-8574-86b6e9d80704-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
[Cc Roman - initial email is http://lkml.kernel.org/r/e6927a82-949c-bdfd-d717-0a14743c6759-hv44wF8Li93QT0dZR+AlfA@public.gmane.org]
On Wed 13-05-20 19:19:56, Li Zefan wrote:
> On 2020/5/13 17:05, Michal Hocko wrote:
> > On Wed 13-05-20 15:28:28, Li Zefan wrote:
> >> While trying to use remote memcg charging in an out-of-tree kernel module
> >> I found it's not working, because the current thread is a workqueue thread.
> >>
> >> Signed-off-by: Zefan Li <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
> >> ---
> >>
> >> No need to queue this for v5.7 as currently no upstream users of this memcg
> >> feature suffer from this bug.
> >>
> >> ---
> >> mm/memcontrol.c | 2 ++
> >> 1 file changed, 2 insertions(+)
> >>
> >> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> >> index a3b97f1..db836fc 100644
> >> --- a/mm/memcontrol.c
> >> +++ b/mm/memcontrol.c
> >> @@ -2802,6 +2802,8 @@ static void memcg_schedule_kmem_cache_create(struct mem_cgroup *memcg,
> >>
> >> static inline bool memcg_kmem_bypass(void)
> >> {
> >> + if (unlikely(current->active_memcg))
> >> + return false;
> >
> > I am confused. Why the check below is insufficient? It checks for both mm
> > and PF_KTHREAD?
> >
>
> memalloc_use_memcg(memcg);
> alloc_page(GFP_KERNEL_ACCOUNT);
> memalloc_unuse_memcg();
>
> If we run above code in a workqueue thread the memory won't be charged to the specific
> memcg, because memcg_kmem_bypass() returns true in this case.
Ohh, right I have misread your patch. Sorry about that. A comment for
the above branch would make it more clear. Something like
/* Allow memalloc_use_memcg usage from kthread contexts */
On the other hand adding a code for an out of tree code is usually not
welcome. But in this particular case the branch is correct for the
existing code already so I am OK with it. Roman is de-facto kmem
implementation maintainer so I will defer to him.
> >> if (in_interrupt() || !current->mm || (current->flags & PF_KTHREAD))
> >> return true;
> >> return false;
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2020-05-13 11:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 7:28 [PATCH] memcg: Fix memcg_kmem_bypass() for remote memcg charging Zefan Li
[not found] ` <e6927a82-949c-bdfd-d717-0a14743c6759-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2020-05-13 9:05 ` Michal Hocko
[not found] ` <20200513090502.GV29153-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2020-05-13 11:19 ` Zefan Li
[not found] ` <76f71776-d049-7407-8574-86b6e9d80704-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2020-05-13 11:29 ` Michal Hocko [this message]
[not found] ` <20200513112905.GX29153-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2020-05-13 11:47 ` [PATCH v2] " Zefan Li
[not found] ` <3a721f62-5a66-8bc5-247b-5c8b7c51c555-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2020-05-13 12:22 ` Shakeel Butt
2020-05-13 13:05 ` Johannes Weiner
2020-05-13 16:11 ` Roman Gushchin
[not found] ` <20200513161110.GA70427-lLJQVQxiE4uLfgCeKHXN1g2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org>
2020-05-14 1:16 ` Zefan Li
[not found] ` <20e89344-cf00-8b0c-64c3-0ac7efd601e6-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2020-05-14 22:52 ` Roman Gushchin
[not found] ` <20200514225259.GA81563-cx5fftMpWqeCjSd+JxjunQ2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org>
2020-05-15 6:56 ` Michal Hocko
[not found] ` <20200515065645.GD29153-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2020-05-15 8:20 ` Zefan Li
[not found] ` <bad0e16b-7141-94c0-45f6-6ed03926b5f8-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2020-05-15 8:34 ` Michal Hocko
[not found] ` <20200515083458.GK29153-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2020-05-15 16:22 ` Shakeel Butt
[not found] ` <CALvZod64-Yc0firp9C8MNhEaF6FTiKmSx2B3HOrvi8GkyOD-7g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-05-15 17:31 ` Roman Gushchin
2020-05-18 9:13 ` Michal Hocko
2020-05-26 1:25 ` [PATCH v3] " Zefan Li
[not found] ` <1d202a12-26fe-0012-ea14-f025ddcd044a-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2020-05-26 15:53 ` Roman Gushchin
2020-05-27 16:50 ` Shakeel Butt
2020-05-28 14:44 ` Michal Hocko
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=20200513112905.GX29153@dhcp22.suse.cz \
--to=mhocko-dgejt+ai2ygdnm+yrofe0a@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=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=lizefan-hv44wF8Li93QT0dZR+AlfA@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