linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Gix <bgix@codeaurora.org>
To: Anderson Lizardo <anderson.lizardo@openbossa.org>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: [RFC] LE: Low Latency GATT Write-Sign-Cmd
Date: Fri, 18 Nov 2011 12:48:13 -0800	[thread overview]
Message-ID: <4EC6C48D.6070609@codeaurora.org> (raw)
In-Reply-To: <CAJdJm_MHBsEER01OsgdhzYM8WyKuGfxHUZwDv-oYQjJtR9N_ww@mail.gmail.com>

Hi Anderson,

On 11/18/2011 12:36 PM, Anderson Lizardo wrote:
> Hi Marcel,
>
> On Fri, Nov 18, 2011 at 3:08 PM, Marcel Holtmann<marcel@holtmann.org>  wrote:
>> I think one of the most important questions that we have to ask
>> ourselves at some point is if we wanna put ATT into the kernel.
>>
>> The potential candidate that forces us to think about this is HID over
>> Low Energy. However I like to see numbers on how the context switches
>> with keeping ATT in userspace will effect our latency.
>
> I still fail to see how ATT handling in kernel would reduce context
> switches. A GATT operation is composed of one or more (possibly many,
> see e.g. discovery procedures) ATT PDUs.
>
> Unless you are proposing GATT on kernel as well?

I don't think having GATT in the kernel is necessarily the logical 
conclusion to an ATT-to-kernel migration.

Remember that the focus of LE is *not* the discovery process.  Discovery 
(of Devices, Services and Characteristics) is important, but what makes 
LE "Low Energy" is what happens *after* pairing and discovery have been 
completed, which ideally would happen One Time Only.

The LE profiles and services are being spec'd so that they can be highly 
efficient over the lifetime of the Low Energy device.  The Linux side of 
the equation will rarely be an actual Low Energy device:  It will just 
know how to talk to an LE device in such a way as to make that 
Button-cell battery driven device last a couple years if possible.

For that reason MOST day-to-day communication between a Linux based 
"Central" device will in fact be single-ATT procedures.  If it takes 
more energy and context switches to do discovery using many compound 
procedures, then we pay that price, because it should only happens Once.

HID devices in particular, will almost certainly NOT use compound GATT 
procedures to communicate after the pairing and discovery point in time 
has past.


-- 
Brian Gix
bgix@codeaurora.org
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum

  reply	other threads:[~2011-11-18 20:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-18 18:17 [RFC] LE: Low Latency GATT Write-Sign-Cmd Brian Gix
2011-11-18 19:08 ` Marcel Holtmann
2011-11-18 19:58   ` Brian Gix
2011-11-18 20:12     ` Johan Hedberg
2011-11-18 20:19       ` Brian Gix
2011-11-18 23:50       ` Vinicius Costa Gomes
2011-11-18 20:36   ` Anderson Lizardo
2011-11-18 20:48     ` Brian Gix [this message]
2011-11-18 20:58       ` Anderson Lizardo
2011-11-18 21:16         ` Brian Gix

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=4EC6C48D.6070609@codeaurora.org \
    --to=bgix@codeaurora.org \
    --cc=anderson.lizardo@openbossa.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    /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;
as well as URLs for NNTP newsgroup(s).