[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANn89iJDMuzUDP=NBk+nV-i7kWqsLyXFY4KyXehr3_pdsp5qGw@mail.gmail.com>
Date: Thu, 16 Oct 2025 11:01:08 -0700
From: Eric Dumazet <edumazet@...gle.com>
To: Simon Horman <horms@...nel.org>
Cc: Florian Westphal <fw@...len.de>, netdev@...r.kernel.org, Paolo Abeni <pabeni@...hat.com>,
"David S. Miller" <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>
Subject: Re: [PATCH net-next] net: Kconfig: discourage drop_monitor enablement
On Thu, Oct 16, 2025 at 9:58 AM Simon Horman <horms@...nel.org> wrote:
>
> On Thu, Oct 16, 2025 at 01:51:47PM +0200, Florian Westphal 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.
> >
> > Signed-off-by: Florian Westphal <fw@...len.de>
>
> I think it is always good to guide people in the right direction.
>
> Reviewed-by: Simon Horman <horms@...nel.org>
Thanks Florian :)
Reviewed-by: Eric Dumazet <edumazet@...gle.com>
Powered by blists - more mailing lists