From: patchwork-bot+bluetooth@kernel.org
To: Wei Deng <wei.deng@oss.qualcomm.com>
Cc: linux-bluetooth@vger.kernel.org, luiz.von.dentz@intel.com,
cheng.jiang@oss.qualcomm.com, jinwang.li@oss.qualcomm.com,
shuai.zhang@oss.qualcomm.com
Subject: Re: [PATCH v3] profile: Set L2CAP IMTU for OBEX profile listeners
Date: Thu, 04 Jun 2026 18:10:07 +0000 [thread overview]
Message-ID: <178059660738.2966613.14116596268653434566.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260604093024.3594022-1-wei.deng@oss.qualcomm.com>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 4 Jun 2026 15:00:24 +0530 you wrote:
> The default_settings entries for OBEX profiles (OPP, FTP, PBAP, MAS,
> MNS) have no imtu field, so ext_start_servers() creates the L2CAP
> listening socket without an explicit IMTU. This causes the socket to
> advertise the L2CAP minimum of 672 bytes in L2CAP_CONFIGURATION_RSP,
> limiting the peer's outgoing PDU size and degrading Rx throughput.
>
> Add an imtu field to default_settings and set it to 32767 for all
> OBEX profiles that use L2CAP. Copy the value in ext_set_defaults()
> and apply it to the listening socket via bt_io_set() after
> bt_io_listen() succeeds.
>
> [...]
Here is the summary with links:
- [v3] profile: Set L2CAP IMTU for OBEX profile listeners
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=646014a6a246
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-06-04 18:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 5:40 [PATCH v1] profile: Set L2CAP IMTU for external profile listeners Wei Deng
2026-05-22 8:37 ` [v1] " bluez.test.bot
2026-06-02 3:17 ` [PATCH v2] " Wei Deng
2026-06-02 7:08 ` [v2] " bluez.test.bot
2026-06-02 14:21 ` [PATCH v2] " Luiz Augusto von Dentz
2026-06-02 14:42 ` Luiz Augusto von Dentz
2026-06-03 13:31 ` Wei Deng
2026-06-04 9:30 ` [PATCH v3] profile: Set L2CAP IMTU for OBEX " Wei Deng
2026-06-04 12:09 ` [v3] " bluez.test.bot
2026-06-04 18:10 ` patchwork-bot+bluetooth [this message]
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=178059660738.2966613.14116596268653434566.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=cheng.jiang@oss.qualcomm.com \
--cc=jinwang.li@oss.qualcomm.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.von.dentz@intel.com \
--cc=shuai.zhang@oss.qualcomm.com \
--cc=wei.deng@oss.qualcomm.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