Linux bluetooth development
 help / color / mirror / Atom feed
* [bluez/bluez] 4756b9: profile: Set L2CAP IMTU for external profile liste...
@ 2026-05-22  8:01 github-actions[bot]
  0 siblings, 0 replies; only message in thread
From: github-actions[bot] @ 2026-05-22  8:01 UTC (permalink / raw)
  To: linux-bluetooth

  Branch: refs/heads/1099144
  Home:   https://github.com/bluez/bluez
  Commit: 4756b963976b8c9c4406e0ee2e6a44c4f754a2cd
      https://github.com/bluez/bluez/commit/4756b963976b8c9c4406e0ee2e6a44c4f754a2cd
  Author: Wei Deng <wei.deng@oss.qualcomm.com>
  Date:   2026-05-22 (Fri, 22 May 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, causing the
socket to default to the L2CAP minimum of 672 bytes. This is advertised
to the peer in L2CAP_CONFIGURATION_RSP and limits PDU size, degrading
Rx throughput.

The obexd client side (obexd/client/bluetooth.c) already sets IMTU to
BT_RX_MTU (32767) when connecting. Mirror that on the server side by
setting BT_IO_OPT_IMTU to 32767 in ext_start_servers().

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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2026-05-22  8:01 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-05-22  8:01 [bluez/bluez] 4756b9: profile: Set L2CAP IMTU for external profile liste github-actions[bot]

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox