How fastos/tcpdive works
tcpdive profiles live Linux TCP traffic with SystemTap, producing per-connection indicators across transmission, loss and retransmission, congestion control, and HTTP processing. Users can run the service or invoke the flexible script with selected modules and filters. The README documents these capabilities, but no source excerpts were provided, so internal calls and dispatch among the scripts are not asserted; auxiliary probes are shown as components without inferred connections.
Main entry points: tcpdive.sh Profiling Runner · tcpdive Service Control · send.stp Transmission · retrans.stp Loss and Retransmission
Components 17
Operation
- Service Control
script/tcpdive - Profiling Runner
tcpdive.sh
TCP Profiling
- Transmission
src/send.stp - Receive
src/recv.stp
Analysis Dimensions
- Loss and Retransmission
src/retrans.stp - Congestion Control
src/congestion.stp - HTTP Processing
src/http.stp
Supporting Probes
- Connection State
src/estab.stp - Connection Close
src/close.stp - Reset Events
src/reset.stp - RTT Probes
src/rtt.stp - TCP Options
src/options.stp - Memory Probes
src/memory.stp - Shared Probes
src/share.stp - TCP Structures
src/structs.stp
Other components
- Operator
- SystemTap Runtime
Connections 7
- Operator → Service Control: controls
README.md - Operator → Profiling Runner: invokes
README.md - Profiling Runner → SystemTap Runtime: runs with
- Profiling Runner → Transmission: selects modules
- Profiling Runner → Loss and Retransmission: selects modules
- Profiling Runner → Congestion Control: selects modules
- Profiling Runner → HTTP Processing: selects modules