From: patchwork-bot+netdevbpf@kernel.org
To: Alexander Lobakin <alobakin@pm.me>
Cc: davem@davemloft.net, kuba@kernel.org, jhubbard@nvidia.com,
rientjes@google.com, yisen.zhuang@huawei.com,
salil.mehta@huawei.com, jesse.brandeburg@intel.com,
anthony.l.nguyen@intel.com, saeedm@nvidia.com, leon@kernel.org,
akpm@linux-foundation.org, brouer@redhat.com,
ilias.apalodimas@linaro.org, jonathan.lemon@gmail.com,
willemb@google.com, rdunlap@infradead.org, pablo@netfilter.org,
decui@microsoft.com, jakub@cloudflare.com, elver@google.com,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
linux-rdma@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH RESEND v3 net-next 0/5] net: consolidate page_is_pfmemalloc() usage
Date: Fri, 05 Feb 2021 02:40:07 +0000 [thread overview]
Message-ID: <161249280746.9463.15568343687164067943.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210202133030.5760-1-alobakin@pm.me>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Tue, 02 Feb 2021 13:30:43 +0000 you wrote:
> page_is_pfmemalloc() is used mostly by networking drivers to test
> if a page can be considered for reusing/recycling.
> It doesn't write anything to the struct page itself, so its sole
> argument can be constified, as well as the first argument of
> skb_propagate_pfmemalloc().
> In Page Pool core code, it can be simply inlined instead.
> Most of the callers from NIC drivers were just doppelgangers of
> the same condition tests. Derive them into a new common function
> do deduplicate the code.
>
> [...]
Here is the summary with links:
- [RESEND,v3,net-next,1/5] mm: constify page_is_pfmemalloc() argument
https://git.kernel.org/netdev/net-next/c/1d7bab6a9445
- [RESEND,v3,net-next,2/5] skbuff: constify skb_propagate_pfmemalloc() "page" argument
https://git.kernel.org/netdev/net-next/c/48f971c9c80a
- [RESEND,v3,net-next,3/5] net: introduce common dev_page_is_reusable()
https://git.kernel.org/netdev/net-next/c/bc38f30f8dbc
- [RESEND,v3,net-next,4/5] net: use the new dev_page_is_reusable() instead of private versions
https://git.kernel.org/netdev/net-next/c/a79afa78e625
- [RESEND,v3,net-next,5/5] net: page_pool: simplify page recycling condition tests
https://git.kernel.org/netdev/net-next/c/05656132a874
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-02-05 2:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 13:30 Alexander Lobakin
2021-02-02 13:30 ` [PATCH RESEND v3 net-next 1/5] mm: constify page_is_pfmemalloc() argument Alexander Lobakin
2021-02-02 13:31 ` [PATCH RESEND v3 net-next 2/5] skbuff: constify skb_propagate_pfmemalloc() "page" argument Alexander Lobakin
2021-02-02 13:31 ` [PATCH RESEND v3 net-next 3/5] net: introduce common dev_page_is_reusable() Alexander Lobakin
2021-02-02 13:31 ` [PATCH RESEND v3 net-next 4/5] net: use the new dev_page_is_reusable() instead of private versions Alexander Lobakin
2021-02-04 19:52 ` Jesse Brandeburg
2021-02-02 13:31 ` [PATCH RESEND v3 net-next 5/5] net: page_pool: simplify page recycling condition tests Alexander Lobakin
2021-02-05 2:40 ` 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=161249280746.9463.15568343687164067943.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alobakin@pm.me \
--cc=anthony.l.nguyen@intel.com \
--cc=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=elver@google.com \
--cc=ilias.apalodimas@linaro.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jakub@cloudflare.com \
--cc=jesse.brandeburg@intel.com \
--cc=jhubbard@nvidia.com \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=rdunlap@infradead.org \
--cc=rientjes@google.com \
--cc=saeedm@nvidia.com \
--cc=salil.mehta@huawei.com \
--cc=willemb@google.com \
--cc=yisen.zhuang@huawei.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