Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH memcg v2] memcg: accounting for objects allocated for new
 netdevice
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <165172261402.3043.8768888843456379249.git-patchwork-notify@kernel.org>
Date:   Thu, 05 May 2022 03:50:14 +0000
References: <354a0a5f-9ec3-a25c-3215-304eab2157bc@openvz.org>
In-Reply-To: <354a0a5f-9ec3-a25c-3215-304eab2157bc@openvz.org>
To:     Vasily Averin <vvs@openvz.org>
Cc:     shakeelb@google.com, kernel@openvz.org, fw@strlen.de,
        linux-kernel@vger.kernel.org, roman.gushchin@linux.dev,
        vbabka@suse.cz, mhocko@suse.com, cgroups@vger.kernel.org,
        netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
        pabeni@redhat.com, mcgrof@kernel.org, keescook@chromium.org,
        yzaikin@google.com, linux-fsdevel@vger.kernel.org
Precedence: bulk

Hello:

This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 2 May 2022 15:15:51 +0300 you wrote:
> Creating a new netdevice allocates at least ~50Kb of memory for various
> kernel objects, but only ~5Kb of them are accounted to memcg. As a result,
> creating an unlimited number of netdevice inside a memcg-limited container
> does not fall within memcg restrictions, consumes a significant part
> of the host's memory, can cause global OOM and lead to random kills of
> host processes.
> 
> [...]

Here is the summary with links:
  - [memcg,v2] memcg: accounting for objects allocated for new netdevice
    https://git.kernel.org/netdev/net-next/c/425b9c7f51c9

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html