From: Vasily Averin <vvs@virtuozzo.com>
To: Shakeel Butt <shakeelb@google.com>, Yutian Yang <nglaive@gmail.com>
Cc: Michal Hocko <mhocko@kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Cgroups <cgroups@vger.kernel.org>, Linux MM <linux-mm@kvack.org>,
shenwenbo@zju.edu.cn
Subject: Re: [PATCH] memcg: charge semaphores and sem_undo objects
Date: Fri, 16 Jul 2021 06:57:19 +0300 [thread overview]
Message-ID: <44325e3a-f4e9-c19a-4a00-672d1d61120d@virtuozzo.com> (raw)
In-Reply-To: <CALvZod4-Vh4O4-PN661jqicSg95GPf87nv10xAYr1yG6oZQk8A@mail.gmail.com>
On 7/15/21 8:05 PM, Shakeel Butt wrote:
> On Thu, Jul 15, 2021 at 12:15 AM Yutian Yang <nglaive@gmail.com> wrote:
>> Signed-off-by: Yutian Yang <nglaive@gmail.com>
>
> Thanks for the patch Yutian. I remember patch from Vasily regarding
> memcg charging of similar objects.
Yes, it is part of my "memcg: enable accounting of ipc resources" patch.
We account few other IPC objects too.
> Vasily, what's the status of your patch?
It is still not merged, unfortunately, I will try to push it again.
Thank you,
Vasily Averin
WARNING: multiple messages have this Message-ID (diff)
From: Vasily Averin <vvs-5HdwGun5lf+gSpxsJD1C4w@public.gmane.org>
To: Shakeel Butt <shakeelb-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
Yutian Yang <nglaive-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Michal Hocko <mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>,
Vladimir Davydov
<vdavydov.dev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Cgroups <cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux MM <linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org>,
shenwenbo-Y5EWUtBUdg4nDS1+zs4M5A@public.gmane.org
Subject: Re: [PATCH] memcg: charge semaphores and sem_undo objects
Date: Fri, 16 Jul 2021 06:57:19 +0300 [thread overview]
Message-ID: <44325e3a-f4e9-c19a-4a00-672d1d61120d@virtuozzo.com> (raw)
In-Reply-To: <CALvZod4-Vh4O4-PN661jqicSg95GPf87nv10xAYr1yG6oZQk8A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 7/15/21 8:05 PM, Shakeel Butt wrote:
> On Thu, Jul 15, 2021 at 12:15 AM Yutian Yang <nglaive-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>> Signed-off-by: Yutian Yang <nglaive-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>
> Thanks for the patch Yutian. I remember patch from Vasily regarding
> memcg charging of similar objects.
Yes, it is part of my "memcg: enable accounting of ipc resources" patch.
We account few other IPC objects too.
> Vasily, what's the status of your patch?
It is still not merged, unfortunately, I will try to push it again.
Thank you,
Vasily Averin
next prev parent reply other threads:[~2021-07-16 3:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 7:14 [PATCH] memcg: charge semaphores and sem_undo objects Yutian Yang
2021-07-15 7:14 ` Yutian Yang
2021-07-15 17:05 ` Shakeel Butt
2021-07-15 17:05 ` Shakeel Butt
2021-07-16 3:57 ` Vasily Averin [this message]
2021-07-16 3:57 ` Vasily Averin
2021-07-15 17:49 ` Matthew Wilcox
2021-07-15 17:49 ` Matthew Wilcox
2021-07-15 18:22 ` Shakeel Butt
2021-07-15 18:22 ` Shakeel Butt
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=44325e3a-f4e9-c19a-4a00-672d1d61120d@virtuozzo.com \
--to=vvs@virtuozzo.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=nglaive@gmail.com \
--cc=shakeelb@google.com \
--cc=shenwenbo@zju.edu.cn \
--cc=vdavydov.dev@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.