From: patchwork-bot+netdevbpf@kernel.org
To: Vasily Averin <vvs@openvz.org>
Cc: kuba@kernel.org, roman.gushchin@linux.dev, vbabka@suse.cz,
shakeelb@google.com, kernel@openvz.org,
linux-kernel@vger.kernel.org, mhocko@suse.com,
cgroups@vger.kernel.org, netdev@vger.kernel.org,
davem@davemloft.net, pabeni@redhat.com
Subject: Re: [PATCH net] net: enable memcg accounting for veth queues
Date: Sun, 01 May 2022 12:20:12 +0000 [thread overview]
Message-ID: <165140761218.13523.5811947461651207574.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <0b28d49b-605c-ac1a-df85-643164e69039@openvz.org>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 29 Apr 2022 08:17:35 +0300 you wrote:
> veth netdevice defines own rx queues and allocates array containing
> up to 4095 ~750-bytes-long 'struct veth_rq' elements. Such allocation
> is quite huge and should be accounted to memcg.
>
> Signed-off-by: Vasily Averin <vvs@openvz.org>
> ---
> drivers/net/veth.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Here is the summary with links:
- [net] net: enable memcg accounting for veth queues
https://git.kernel.org/netdev/net-next/c/961c6136359e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-05-01 12:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 10:34 [PATCH] memcg: enable accounting for veth queues Vasily Averin
2022-04-27 16:58 ` Jakub Kicinski
2022-04-27 22:48 ` Vasily Averin
2022-04-29 5:17 ` [PATCH net] net: enable memcg " Vasily Averin
2022-05-01 12:20 ` patchwork-bot+netdevbpf [this message]
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=165140761218.13523.5811947461651207574.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=kernel@openvz.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=roman.gushchin@linux.dev \
--cc=shakeelb@google.com \
--cc=vbabka@suse.cz \
--cc=vvs@openvz.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