From: patchwork-bot+netdevbpf@kernel.org
To: Florian Westphal <fw@strlen.de>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, horms@kernel.org
Subject: Re: [PATCH net-next] net: Kconfig: discourage drop_monitor enablement
Date: Fri, 17 Oct 2025 23:40:12 +0000 [thread overview]
Message-ID: <176074441201.2826097.18118475897010397412.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251016115147.18503-1-fw@strlen.de>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 16 Oct 2025 13:51:47 +0200 you wrote:
> Quoting Eric Dumazet:
> "I do not understand the fascination with net/core/drop_monitor.c [..]
> misses all the features, flexibility, scalability that 'perf',
> eBPF tracing, bpftrace, .... have today."
>
> Reword DROP_MONITOR kconfig help text to clearly state that its not
> related to perf-based drop monitoring and that its safe to disable
> this unless support for the older netlink-based tools is needed.
>
> [...]
Here is the summary with links:
- [net-next] net: Kconfig: discourage drop_monitor enablement
https://git.kernel.org/netdev/net-next/c/2af8ff1e472e
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:[~2025-10-17 23:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 11:51 [PATCH net-next] net: Kconfig: discourage drop_monitor enablement Florian Westphal
2025-10-16 16:58 ` Simon Horman
2025-10-16 18:01 ` Eric Dumazet
2025-10-17 23: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=176074441201.2826097.18118475897010397412.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--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 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).