From: Szymon Janc <ext.szymon.janc@tieto.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "Łukasz Rymanowski" <lukasz.rymanowski@codecoup.pl>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH BlueZ 2/2] core/device: Don't set MTU when acting as a peripheral
Date: Thu, 10 Mar 2016 10:42:05 +0100 [thread overview]
Message-ID: <4446282.74ti4cqF2s@leonov> (raw)
In-Reply-To: <CABBYNZKNkEFO7uAsH55Un47esqezPV-acTiqE1NFMfNXFWKj2Q@mail.gmail.com>
Hi Luiz,
On Thursday 10 of March 2016 11:35:23 Luiz Augusto von Dentz wrote:
> Hi Lukasz,
>
> On Thu, Mar 10, 2016 at 11:17 AM, Łukasz Rymanowski
>
> <lukasz.rymanowski@codecoup.pl> wrote:
> >> Not only we cannot be configured as server, but even if we do the
> >> roles are only relevant for PTS because otherwise there is no way to
> >> tell the roles of the remote device.
> >
> > If device sends request that means it is a Client. If not that means
> > it is a Server.
>
> Well if it send it can be a Client/Server as well, btw some systems
> including Android appear to have support to send Exchange MTU at any
> point so detecting a server only pretty hard, besides our current
> design split Server and Client functionality so waiting to see if
> anything has been received before starting sending anything is not so
> trivial and we had still to choose an arbitrary timeout to wait for
> detecting the role but if both are based on BlueZ this would just
> delay each other.
Maybe we could simply delay MTU exchange until we are done with discovery?
For discovery we shouldn't need larger MTU. And if in the meantime remote
initiates MTU exchange we can skip MTU exchange from our side.
--
BR
Szymon Janc
next prev parent reply other threads:[~2016-03-10 9:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 12:24 [PATCH BlueZ 1/2] shared/gatt-client: Don't send Exchange MTU for default value Luiz Augusto von Dentz
2016-03-04 12:24 ` [PATCH BlueZ 2/2] core/device: Don't set MTU when acting as a peripheral Luiz Augusto von Dentz
2016-03-04 12:51 ` Łukasz Rymanowski
2016-03-04 13:12 ` Luiz Augusto von Dentz
2016-03-04 13:35 ` Szymon Janc
2016-03-04 14:38 ` Luiz Augusto von Dentz
2016-03-04 15:46 ` Łukasz Rymanowski
2016-03-09 12:13 ` Luiz Augusto von Dentz
2016-03-10 7:59 ` Łukasz Rymanowski
2016-03-10 8:30 ` Luiz Augusto von Dentz
2016-03-10 9:17 ` Łukasz Rymanowski
2016-03-10 9:35 ` Luiz Augusto von Dentz
2016-03-10 9:42 ` Szymon Janc [this message]
2016-03-10 10:26 ` Luiz Augusto von Dentz
2016-03-11 14:46 ` Luiz Augusto von Dentz
2016-03-11 14:44 ` [PATCH BlueZ 1/2] shared/gatt-client: Don't send Exchange MTU for default value Luiz Augusto von Dentz
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=4446282.74ti4cqF2s@leonov \
--to=ext.szymon.janc@tieto.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=lukasz.rymanowski@codecoup.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.