From: patchwork-bot+netdevbpf@kernel.org
To: Talal Ahmad <mailtalalahmad@gmail.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, arjunroy@google.com,
edumazet@google.com, soheil@google.com, willemb@google.com,
dsahern@kernel.org, yoshfuji@linux-ipv6.org, kuba@kernel.org,
cong.wang@bytedance.com, haokexin@gmail.com,
jonathan.lemon@gmail.com, alobakin@pm.me, pabeni@redhat.com,
ilias.apalodimas@linaro.org, memxor@gmail.com, elver@google.com,
nogikh@google.com, vvs@virtuozzo.com, talalahmad@google.com
Subject: Re: [PATCH net-next v3] net: avoid double accounting for pure zerocopy skbs
Date: Wed, 03 Nov 2021 14:10:08 +0000 [thread overview]
Message-ID: <163594860815.30241.9867591652285399304.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211103025844.2579722-1-mailtalalahmad@gmail.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 2 Nov 2021 22:58:44 -0400 you wrote:
> From: Talal Ahmad <talalahmad@google.com>
>
> Track skbs containing only zerocopy data and avoid charging them to
> kernel memory to correctly account the memory utilization for
> msg_zerocopy. All of the data in such skbs is held in user pages which
> are already accounted to user. Before this change, they are charged
> again in kernel in __zerocopy_sg_from_iter. The charging in kernel is
> excessive because data is not being copied into skb frags. This
> excessive charging can lead to kernel going into memory pressure
> state which impacts all sockets in the system adversely. Mark pure
> zerocopy skbs with a SKBFL_PURE_ZEROCOPY flag and remove
> charge/uncharge for data in such skbs.
>
> [...]
Here is the summary with links:
- [net-next,v3] net: avoid double accounting for pure zerocopy skbs
https://git.kernel.org/netdev/net/c/9b65b17db723
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:[~2021-11-03 14:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 2:58 [PATCH net-next v3] net: avoid double accounting for pure zerocopy skbs Talal Ahmad
2021-11-03 14:10 ` 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=163594860815.30241.9867591652285399304.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alobakin@pm.me \
--cc=arjunroy@google.com \
--cc=cong.wang@bytedance.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=elver@google.com \
--cc=haokexin@gmail.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=mailtalalahmad@gmail.com \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nogikh@google.com \
--cc=pabeni@redhat.com \
--cc=soheil@google.com \
--cc=talalahmad@google.com \
--cc=vvs@virtuozzo.com \
--cc=willemb@google.com \
--cc=yoshfuji@linux-ipv6.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 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.