netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: David Awogbemila <awogbemila@google.com>
Cc: netdev@vger.kernel.org, jeroendb@google.com, csully@google.com
Subject: Re: [PATCH net] gve: Fix GFP flags when allocing pages
Date: Thu, 27 Jan 2022 02:50:10 +0000	[thread overview]
Message-ID: <164325181034.16805.1401074570855321284.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220126003843.3584521-1-awogbemila@google.com>

Hello:

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

On Tue, 25 Jan 2022 16:38:43 -0800 you wrote:
> From: Catherine Sullivan <csully@google.com>
> 
> Use GFP_ATOMIC when allocating pages out of the hotpath,
> continue to use GFP_KERNEL when allocating pages during setup.
> 
> GFP_KERNEL will allow blocking which allows it to succeed
> more often in a low memory enviornment but in the hotpath we do
> not want to allow the allocation to block.
> 
> [...]

Here is the summary with links:
  - [net] gve: Fix GFP flags when allocing pages
    https://git.kernel.org/netdev/net/c/a92f7a6feeb3

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



  reply	other threads:[~2022-01-27  2:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26  0:38 [PATCH net] gve: Fix GFP flags when allocing pages David Awogbemila
2022-01-27  2:50 ` patchwork-bot+netdevbpf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-09-13  0:09 Jeroen de Borst
2022-09-20  1:40 ` patchwork-bot+netdevbpf

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=164325181034.16805.1401074570855321284.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=awogbemila@google.com \
    --cc=csully@google.com \
    --cc=jeroendb@google.com \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).