* [bluez/bluez] 6b4c21: monitor: Add L2CAP channel details to analyze output
@ 2026-04-16 14:09 hadess
0 siblings, 0 replies; only message in thread
From: hadess @ 2026-04-16 14:09 UTC (permalink / raw)
To: linux-bluetooth
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 6b4c21721c80ef09da17656920777a4f1a9bf293
https://github.com/bluez/bluez/commit/6b4c21721c80ef09da17656920777a4f1a9bf293
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-04-15 (Wed, 15 Apr 2026)
Changed paths:
M monitor/analyze.c
Log Message:
-----------
monitor: Add L2CAP channel details to analyze output
Enhance btmon analyze mode to display richer per-channel information:
- Add MTU, MPS, and mode fields to struct l2cap_chan
- Parse Configure Request/Response options for BR/EDR channels to
extract MTU (option 0x01) and mode (option 0x04)
- Add l2cap_le_sig() to parse LE signaling (CID 5) for LE Credit
Based Connection Request/Response and Enhanced Credit Connection
Request, extracting PSM, MTU, MPS, and mode
- Display fixed channel names (ATT, L2CAP Signaling, SMP) for CID <= 7
- Show PSM in both decimal and hex format
- Print mode, MTU, and MPS for dynamic channels
Commit: ebeceecd3ccb823d46427a975563987242eaa6f5
https://github.com/bluez/bluez/commit/ebeceecd3ccb823d46427a975563987242eaa6f5
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-04-15 (Wed, 15 Apr 2026)
Changed paths:
M monitor/analyze.c
Log Message:
-----------
monitor: Use wall-clock duration for throughput and add min/max speed
The previous speed calculation used the sum of per-packet latencies as
the denominator. For TX, each latency measures the time from command
submission to completion event -- when multiple packets are in-flight
simultaneously these overlap, making the sum much larger than wall-clock
time and deflating the reported speed. For RX the inter-arrival sum
roughly equals wall-clock time. This asymmetry caused the same data
stream to report vastly different speeds depending on direction.
Fix by computing speed from wall-clock duration (last packet timestamp
minus first packet timestamp), which gives consistent results regardless
of direction. Also add 1-second windowed throughput tracking to report
min and max speed alongside the average.
Commit: f360d9e4428dde40de4ff6d33ef178752e13fc1a
https://github.com/bluez/bluez/commit/f360d9e4428dde40de4ff6d33ef178752e13fc1a
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-04-15 (Wed, 15 Apr 2026)
Changed paths:
M doc/btmon-l2cap.rst
Log Message:
-----------
doc: Add throughput estimation section to btmon-l2cap.rst
Document the throughput statistics reported by btmon analyze mode,
including speed calculation methodology, channel details (PSM, mode,
MTU, MPS), and caveats about inter-packet latency vs wall-clock time.
Also document the windowed throughput approach used by btsnoop-analyzer.
Commit: 590bed15fbaf7be93f5121fcdaf12992f234df13
https://github.com/bluez/bluez/commit/590bed15fbaf7be93f5121fcdaf12992f234df13
Author: Bastien Nocera <hadess@hadess.net>
Date: 2026-04-16 (Thu, 16 Apr 2026)
Changed paths:
M Makefile.am
M doc/btmon.rst
Log Message:
-----------
doc: Add missing btmon-cs doc to btmon.rst
Compare: https://github.com/bluez/bluez/compare/510623fb53b5...590bed15fbaf
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2026-04-16 14:09 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-04-16 14:09 [bluez/bluez] 6b4c21: monitor: Add L2CAP channel details to analyze output hadess
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox