From: patchwork-bot+netdevbpf@kernel.org
To: Wei Wang <weiwan@google.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
cgroups@vger.kernel.org, linux-mm@kvack.org, guro@fb.com,
edumazet@google.com, shakeelb@google.com
Subject: Re: [PATCH net-next] net-memcg: pass in gfp_t mask to mem_cgroup_charge_skmem()
Date: Wed, 18 Aug 2021 10:50:05 +0000 [thread overview]
Message-ID: <162928380597.20153.6653369000646773823.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210817194003.2102381-1-weiwan@google.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Tue, 17 Aug 2021 12:40:03 -0700 you wrote:
> Add gfp_t mask as an input parameter to mem_cgroup_charge_skmem(),
> to give more control to the networking stack and enable it to change
> memcg charging behavior. In the future, the networking stack may decide
> to avoid oom-kills when fallbacks are more appropriate.
>
> One behavior change in mem_cgroup_charge_skmem() by this patch is to
> avoid force charging by default and let the caller decide when and if
> force charging is needed through the presence or absence of
> __GFP_NOFAIL.
>
> [...]
Here is the summary with links:
- [net-next] net-memcg: pass in gfp_t mask to mem_cgroup_charge_skmem()
https://git.kernel.org/netdev/net-next/c/4b1327be9fe5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-08-18 10:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 19:40 [PATCH net-next] net-memcg: pass in gfp_t mask to mem_cgroup_charge_skmem() Wei Wang
2021-08-18 10:50 ` patchwork-bot+netdevbpf [this message]
2022-10-12 23:33 ` Jakub Kicinski
2022-10-13 0:17 ` Shakeel Butt
2022-10-13 0:38 ` Jakub Kicinski
2022-10-13 0:54 ` Shakeel Butt
2022-10-13 1:40 ` Jakub Kicinski
2022-10-13 3:16 ` Jakub Kicinski
2022-10-13 3:34 ` Wei Wang
2022-10-13 3:49 ` Jakub Kicinski
2022-10-13 4:04 ` Wei Wang
2022-10-13 4:18 ` Shakeel Butt
2022-10-13 21:49 ` Jakub Kicinski
2022-10-13 22:02 ` Eric Dumazet
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=162928380597.20153.6653369000646773823.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=guro@fb.com \
--cc=kuba@kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=shakeelb@google.com \
--cc=weiwan@google.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;
as well as URLs for NNTP newsgroup(s).