From: Kris Van Hees <kris.van.hees@oracle.com>
To: Eugene Loh <eugene.loh@oracle.com>
Cc: Alan Maguire <alan.maguire@oracle.com>,
dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [PATCH v2 0/4] DTrace TCP provider
Date: Tue, 1 Jul 2025 15:27:33 -0400 [thread overview]
Message-ID: <aGQ2pe0taoYjUy84@oracle.com> (raw)
In-Reply-To: <cd4946a0-f529-d927-24d5-0c468119f000@oracle.com>
On Tue, Jul 01, 2025 at 03:08:59PM -0400, Eugene Loh wrote:
> Incidentally, looking at the subject lines for the patch series, I see:
>
> dtrace: move get_member() to dt_cg.c
> dt_impl: bump number of TSLOTS to 8
> dtrace: add tcp provider
> dtrace: sync dlibs with tcp.d, ip.d and net.d changes
I would suggest:
cg: move get_member() to dt_cg.c
cg: bump number of TSLOTS to 8
tcp: new provider -or- Implement the tcp provider
dlibs: sync dlibs with tcp.d, ip.d and net.d changes
> That is, each line is prefixed with a component name. We do that a lot for
> "test:", but otherwise the practice seems to depend on... the patch author?
> Anyhow, I claim "dtrace:" is not very useful. For patch 1, all the prefix
> is saying is "there is movement in the dtrace code base." I think the
> subject would be more direct without the prefix. Same for patch 2. For
> patch 3, if one wanted to use a component prefix, I'd think one would use
> "tcp:".
>
> Historically, it looks like we've added new providers with subject lines
> like this:
>
> rawfbt: new provider
> Implement the io provider
> Implement the ip provider
> Implement the lockstat provider
> Implement the sched provider (first part)
> Implement the proc provider
> provider: Implement a rawtp provider
> Add a CPC provider
> PID provider implementation
> Add a profile provider
> Implement BEGIN and END probes for the dtrace provider
> Added IO provider support for 4.14 kernels
>
> Everyone has their own style. Shrug. No big deal.
>
> Anyhow, personally, I think the prefixes don't add much, especially for
> "dtrace:". My suggestion is to drop the prefixes, but... your call.
>
> On 6/10/25 09:58, Alan Maguire wrote:
>
> > This series is a first draft of TCP provider support, where the
> > probes are implemented via underlying fbt and sdt probes.
> >
> > Due to the use of the sock/inet_sock_set_state tracepoint, intended
> > for ~5.15 kernels and later. Tried replacing this with
> >
> > fbt::tcp_set_state:entry
> >
> > but this misses a few state transitions, so stuck with using
> > the tracepoint.
> >
> > All tests under test/unittest/tcp pass unmodified on an upstream
> > (6.15) kernel and 5.15 UEK7U3 kernel.
> >
> > It implements all documented TCP provider probes:
> >
> > accept-established, accept-refused, connnect-request,
> > connect-established, connect-refused, receive, send,
> > state-change
> >
> > Changes since RFC:
> >
> > - fixed issues with test failures on UEK7 due to missing
> > SYN_RCV state change
> > - moved get_member() to dt_cg.c (patch 1)
> >
> > Alan Maguire (4):
> > dtrace: move get_member() to dt_cg.c
> > dt_impl: bump number of TSLOTS to 8
> > dtrace: add tcp provider
> > dtrace: sync dlibs with tcp.d, ip.d and net.d changes
> >
> > dlibs/aarch64/5.14/ip.d | 1 -
> > dlibs/aarch64/5.14/net.d | 6 +-
> > dlibs/aarch64/5.14/tcp.d | 52 ++---
> > dlibs/aarch64/5.16/ip.d | 1 -
> > dlibs/aarch64/5.16/net.d | 6 +-
> > dlibs/aarch64/5.16/tcp.d | 52 ++---
> > dlibs/aarch64/6.1/ip.d | 1 -
> > dlibs/aarch64/6.1/net.d | 6 +-
> > dlibs/aarch64/6.1/tcp.d | 52 ++---
> > dlibs/aarch64/6.10/ip.d | 1 -
> > dlibs/aarch64/6.10/net.d | 6 +-
> > dlibs/aarch64/6.10/tcp.d | 52 ++---
> > dlibs/x86_64/5.14/ip.d | 1 -
> > dlibs/x86_64/5.14/net.d | 6 +-
> > dlibs/x86_64/5.14/tcp.d | 52 ++---
> > dlibs/x86_64/5.16/ip.d | 1 -
> > dlibs/x86_64/5.16/net.d | 6 +-
> > dlibs/x86_64/5.16/tcp.d | 52 ++---
> > dlibs/x86_64/6.1/ip.d | 1 -
> > dlibs/x86_64/6.1/net.d | 6 +-
> > dlibs/x86_64/6.1/tcp.d | 52 ++---
> > dlibs/x86_64/6.10/ip.d | 1 -
> > dlibs/x86_64/6.10/net.d | 6 +-
> > dlibs/x86_64/6.10/tcp.d | 52 ++---
> > libdtrace/Build | 2 +
> > libdtrace/dt_cg.c | 39 ++++
> > libdtrace/dt_cg.h | 2 +
> > libdtrace/dt_impl.h | 2 +-
> > libdtrace/dt_prov_ip.c | 45 +----
> > libdtrace/dt_prov_tcp.c | 405 +++++++++++++++++++++++++++++++++++++++
> > libdtrace/dt_provider.c | 1 +
> > libdtrace/dt_provider.h | 1 +
> > libdtrace/ip.d | 1 -
> > libdtrace/net.d | 6 +-
> > libdtrace/tcp.d | 52 ++---
> > 35 files changed, 761 insertions(+), 267 deletions(-)
> > create mode 100644 libdtrace/dt_prov_tcp.c
> >
next prev parent reply other threads:[~2025-07-01 19:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 13:58 [PATCH v2 0/4] DTrace TCP provider Alan Maguire
2025-06-10 13:58 ` [PATCH v2 1/4] dtrace: move get_member() to dt_cg.c Alan Maguire
2025-07-01 18:23 ` Eugene Loh
2025-06-10 13:58 ` [PATCH v2 2/4] dt_impl: bump number of TSLOTS to 8 Alan Maguire
2025-07-01 18:31 ` Eugene Loh
2025-07-02 14:52 ` Alan Maguire
2025-07-02 20:22 ` Eugene Loh
2025-07-03 15:18 ` Alan Maguire
2025-06-10 13:58 ` [PATCH v2 3/4] dtrace: add tcp provider Alan Maguire
2025-07-01 23:16 ` Eugene Loh
2025-07-02 15:06 ` Alan Maguire
2025-07-03 0:02 ` Eugene Loh
2025-07-03 15:03 ` Alan Maguire
2025-07-03 15:29 ` Kris Van Hees
2025-07-03 15:38 ` Kris Van Hees
2025-07-03 19:55 ` Eugene Loh
2025-07-07 18:44 ` Kris Van Hees
2025-06-10 13:58 ` [PATCH v2 4/4] dtrace: sync dlibs with tcp.d, ip.d and net.d changes Alan Maguire
2025-07-01 19:08 ` [PATCH v2 0/4] DTrace TCP provider Eugene Loh
2025-07-01 19:27 ` Kris Van Hees [this message]
2025-07-02 14:52 ` Alan Maguire
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=aGQ2pe0taoYjUy84@oracle.com \
--to=kris.van.hees@oracle.com \
--cc=alan.maguire@oracle.com \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
--cc=eugene.loh@oracle.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