public inbox for cgroups@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
To: Vasily Averin <vvs-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
Cc: kuba-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	roman.gushchin-fxUVXftIFDnyG1zEObXtfA@public.gmane.org,
	vbabka-AlSwsSmVLrQ@public.gmane.org,
	shakeelb-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
	kernel-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	mhocko-IBi9RG/b67k@public.gmane.org,
	cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org,
	pabeni-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
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-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>

Hello:

This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>:

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-GEFAQzZX7r8dnm+yROfE0A@public.gmane.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



      parent reply	other threads:[~2022-05-01 12:20 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
     [not found] ` <1c338b99-8133-6126-2ff2-94a4d3f26451-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2022-04-27 16:58   ` Jakub Kicinski
     [not found]     ` <20220427095854.79554fab-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2022-04-27 22:48       ` Vasily Averin
2022-04-29  5:17       ` [PATCH net] net: enable memcg " Vasily Averin
     [not found]         ` <0b28d49b-605c-ac1a-df85-643164e69039-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2022-05-01 12:20           ` patchwork-bot+netdevbpf-DgEjT+Ai2ygdnm+yROfE0A [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-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
    --cc=kernel-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
    --cc=kuba-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mhocko-IBi9RG/b67k@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=pabeni-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=roman.gushchin-fxUVXftIFDnyG1zEObXtfA@public.gmane.org \
    --cc=shakeelb-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
    --cc=vbabka-AlSwsSmVLrQ@public.gmane.org \
    --cc=vvs-GEFAQzZX7r8dnm+yROfE0A@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