From: Vasily Averin <vvs@virtuozzo.com>
To: Michal Hocko <mhocko@suse.com>
Cc: cgroups@vger.kernel.org, linux-mm@kvack.org,
Johannes Weiner <hannes@cmpxchg.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>
Subject: Re: [PATCH 1/9] memcg: accounting for allocations called with disabled BH
Date: Wed, 10 Mar 2021 12:11:26 +0300 [thread overview]
Message-ID: <60275aa1-082e-af13-b048-76c5a5cf18fb@virtuozzo.com> (raw)
In-Reply-To: <YEeM8AZczZt/irhR@dhcp22.suse.cz>
On 3/9/21 5:57 PM, Michal Hocko wrote:
> On Tue 09-03-21 11:03:48, Vasily Averin wrote:
>> in_interrupt() check in memcg_kmem_bypass() is incorrect because
>> it does not allow to account memory allocation called from task context
>> with disabled BH, i.e. inside spin_lock_bh()/spin_unlock_bh() sections
>
> Is there any existing user in the tree? Or is this more of a preparatory
> patch for a later one which will need it? In other words, is this a bug
> fix or a preparatory work.
struct fib6_node objects are allocated by this way
net/ipv6/route.c::__ip6_ins_rt()
... write_lock_bh(&table->tb6_lock);
err = fib6_add(&table->tb6_root, rt, info, mxc);
write_unlock_bh(&table->tb6_lock);
I spend some time to understand why properly entries from properly configured cache
was not accounted to container's memcg.
Thank you,
Vasily Averin
next prev parent reply other threads:[~2021-03-10 9:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 8:03 Vasily Averin
2021-03-09 14:57 ` Michal Hocko
2021-03-10 9:11 ` Vasily Averin [this message]
2021-03-10 9:40 ` Michal Hocko
2021-03-09 19:39 ` Shakeel Butt
2021-03-09 20:18 ` Roman Gushchin
2021-03-10 9:21 ` Vasily Averin
2021-03-10 9:42 ` Michal Hocko
2021-03-10 19:09 ` Roman Gushchin
2021-03-10 9:17 ` Vasily Averin
2021-03-09 20:39 ` Roman Gushchin
2021-03-10 9:26 ` Vasily Averin
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=60275aa1-082e-af13-b048-76c5a5cf18fb@virtuozzo.com \
--to=vvs@virtuozzo.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox