From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
edumazet@google.com, mathew.j.martineau@linux.intel.com,
matthieu.baerts@tessares.net
Subject: Re: [PATCH net-next 0/2] net: snmp: minor optimizations
Date: Thu, 30 Sep 2021 13:20:10 +0000 [thread overview]
Message-ID: <163300801002.14372.16920403544921536422.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210930010333.2625706-1-eric.dumazet@gmail.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Wed, 29 Sep 2021 18:03:31 -0700 you wrote:
> From: Eric Dumazet <edumazet@google.com>
>
> Fetching many SNMP counters on hosts with large number of cpus
> takes a lot of time. mptcp still uses the old non-batched
> fashion which is not cache friendly.
>
> Eric Dumazet (2):
> net: snmp: inline snmp_get_cpu_field()
> mptcp: use batch snmp operations in mptcp_seq_show()
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: snmp: inline snmp_get_cpu_field()
https://git.kernel.org/netdev/net-next/c/59f09ae8fac4
- [net-next,2/2] mptcp: use batch snmp operations in mptcp_seq_show()
https://git.kernel.org/netdev/net-next/c/acbd0c814413
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-09-30 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 1:03 [PATCH net-next 0/2] net: snmp: minor optimizations Eric Dumazet
2021-09-30 1:03 ` [PATCH net-next 1/2] net: snmp: inline snmp_get_cpu_field() Eric Dumazet
2021-09-30 1:03 ` [PATCH net-next 2/2] mptcp: use batch snmp operations in mptcp_seq_show() Eric Dumazet
2021-09-30 13:20 ` 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=163300801002.14372.16920403544921536422.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=mathew.j.martineau@linux.intel.com \
--cc=matthieu.baerts@tessares.net \
--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 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.