[bluez/bluez] 1b39ef: profile: Set L2CAP IMTU for external profile liste...

[bluez/bluez] 1b39ef: profile: Set L2CAP IMTU for external profile liste...

[github-actions[bot]]

  Branch: refs/heads/1104327
  Home:   https://github.com/bluez/bluez
  Commit: 1b39efe9c30d37330412342b59bce41297d68799
      https://github.com/bluez/bluez/commit/1b39efe9c30d37330412342b59bce41297d68799
  Author: Wei Deng <wei.deng@oss.qualcomm.com>
  Date:   2026-06-02 (Tue, 02 Jun 2026)

  Changed paths:
    M src/profile.c

  Log Message:
  -----------
  profile: Set L2CAP IMTU for external profile listeners

bt_io_listen() in ext_start_servers() creates the L2CAP listening
socket for external profiles without an explicit IMTU. This causes
the socket to use the L2CAP minimum of 672 bytes, which is advertised
to the peer in L2CAP_CONFIGURATION_RSP.

As a result, when acting as a server (receiver), the peer limits its
outgoing PDU size to our advertised 672 bytes. This leads to small
OBEX body chunks (~669 bytes) and severely degraded Rx throughput,
while Tx throughput is unaffected since the peer's IMTU is not
constrained by our setting.

The obexd client side (obexd/client/bluetooth.c) already sets IMTU to
BT_RX_MTU (32767) for outgoing connections. Mirror that on the server
side by setting BT_IO_OPT_IMTU to BT_RX_MTU in ext_start_servers(),
so incoming connections advertise the same maximum receive capability.

Signed-off-by: Wei Deng <wei.deng@oss.qualcomm.com>



To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications