From: patchwork-bot+netdevbpf@kernel.org
To: Guangbin Huang <huangguangbin2@huawei.com>
Cc: davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com, bpf@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, lipeng321@huawei.com,
chenhao288@hisilicon.com
Subject: Re: [PATCH net-next] net: page_pool: add page allocation stats for two fast page allocate path
Date: Fri, 13 May 2022 10:40:16 +0000 [thread overview]
Message-ID: <165243841613.19214.9273427764376965858.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220512065631.33673-1-huangguangbin2@huawei.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 12 May 2022 14:56:31 +0800 you wrote:
> From: Jie Wang <wangjie125@huawei.com>
>
> Currently If use page pool allocation stats to analysis a RX performance
> degradation problem. These stats only count for pages allocate from
> page_pool_alloc_pages. But nic drivers such as hns3 use
> page_pool_dev_alloc_frag to allocate pages, so page stats in this API
> should also be counted.
>
> [...]
Here is the summary with links:
- [net-next] net: page_pool: add page allocation stats for two fast page allocate path
https://git.kernel.org/netdev/net-next/c/0f6deac3a079
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:[~2022-05-13 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 6:56 [PATCH net-next] net: page_pool: add page allocation stats for two fast page allocate path Guangbin Huang
2022-05-13 10: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=165243841613.19214.9273427764376965858.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chenhao288@hisilicon.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=huangguangbin2@huawei.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lipeng321@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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.