[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231205155035.6dd41a13@gandalf.local.home>
Date: Tue, 5 Dec 2023 15:50:35 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Eric Dumazet <edumazet@...gle.com>
Cc: Xuan Zhuo <xuanzhuo@...ux.alibaba.com>, netdev@...r.kernel.org,
mhiramat@...nel.org, mathieu.desnoyers@...icios.com, davem@...emloft.net,
dsahern@...nel.org, kuba@...nel.org, pabeni@...hat.com,
martin.lau@...ux.dev, linux-trace-kernel@...r.kernel.org,
bpf@...r.kernel.org, dust.li@...ux.alibaba.com, alibuda@...ux.alibaba.com,
guwen@...ux.alibaba.com, hengqi@...ux.alibaba.com, Philo Lu
<lulie@...ux.alibaba.com>
Subject: Re: [PATCH net-next] tcp: add tracepoints for data send/recv/acked
On Tue, 5 Dec 2023 20:39:28 +0100
Eric Dumazet <edumazet@...gle.com> wrote:
> > So, we do not want to add some tracepoint to do some unknow debug.
> > We have a clear goal. debugging is just an incidental capability.
> >
>
> We have powerful mechanisms in the stack already that ordinary (no
> privilege requested) applications can readily use.
>
I'm not arguing for or against this patch set, but tracepoints are
available for other utilities that may have non privilege access. They are
not just for tracers.
-- Steve
Powered by blists - more mailing lists