All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	netdev@vger.kernel.org, eric.dumazet@gmail.com,
	idosch@nvidia.com, jiri@nvidia.com
Subject: Re: [PATCH net-next 0/2] rtnetlink: rtnl_stats_dump() changes
Date: Fri, 03 May 2024 22:20:29 +0000	[thread overview]
Message-ID: <171477482947.17287.7673990321275030735.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240502113748.1622637-1-edumazet@google.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu,  2 May 2024 11:37:46 +0000 you wrote:
> Getting rid of RTNL in rtnl_stats_dump() looks challenging.
> 
> In the meantime, we can:
> 
> 1) Avoid RTNL acquisition for the final NLMSG_DONE marker.
> 
> 2) Use for_each_netdev_dump() instead of the net->dev_index_head[]
>    hash table.
> 
> [...]

Here is the summary with links:
  - [net-next,1/2] rtnetlink: change rtnl_stats_dump() return value
    https://git.kernel.org/netdev/net-next/c/136c2a9a2a87
  - [net-next,2/2] rtnetlink: use for_each_netdev_dump() in rtnl_stats_dump()
    https://git.kernel.org/netdev/net-next/c/0feb396f7428

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



      parent reply	other threads:[~2024-05-03 22:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-02 11:37 [PATCH net-next 0/2] rtnetlink: rtnl_stats_dump() changes Eric Dumazet
2024-05-02 11:37 ` [PATCH net-next 1/2] rtnetlink: change rtnl_stats_dump() return value Eric Dumazet
2024-05-02 15:59   ` David Ahern
2024-05-02 16:03     ` Eric Dumazet
2024-05-06 16:23       ` David Ahern
2024-05-06 16:28         ` Eric Dumazet
2024-05-02 11:37 ` [PATCH net-next 2/2] rtnetlink: use for_each_netdev_dump() in rtnl_stats_dump() Eric Dumazet
2024-05-02 16:02   ` David Ahern
2024-05-03 22: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=171477482947.17287.7673990321275030735.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=idosch@nvidia.com \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --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.