linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antti Julku <antti.julku@nokia.com>
To: ext Marcel Holtmann <marcel@holtmann.org>
Cc: Claudio Takahasi <claudio.takahasi@openbossa.org>,
	linux-bluetooth@vger.kernel.org
Subject: Re: Name resolution for mgmt interface
Date: Tue, 13 Sep 2011 09:39:43 +0300	[thread overview]
Message-ID: <4E6EFAAF.3050505@nokia.com> (raw)
In-Reply-To: <1315854441.1937.28.camel@aeonflux>


Hi Marcel,

On 09/12/2011 10:07 PM, ext Marcel Holtmann wrote:

> I honestly don't know which one is easier. We also have to keep the
> memory constraints in mind. So for how many BD_ADDR does the kernel
> needs to store the flag name resolved already yes/no? With system that
> are running for years, this can get pretty big.
>
> My current take on this (which is not final) is that after inquiry
> complete, the kernel needs to ask userspace to confirm which names to
> resolve. It is an action triggered by the kernel and userspace just
> responds with the result to. So the kernel has full control here.
>

Can we assume that user space will always reply? Or how long should 
kernel wait for confirmation from user space, before ending discovery 
procedure and sending Discovering=0 event?

Br,
Antti

  parent reply	other threads:[~2011-09-13  6:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-09 14:36 Name resolution for mgmt interface Antti Julku
2011-09-09 22:19 ` Claudio Takahasi
2011-09-10  6:23   ` Marcel Holtmann
2011-09-12 16:56     ` Claudio Takahasi
2011-09-12 19:07       ` Marcel Holtmann
2011-09-12 19:15         ` tim.howes
2011-09-13  7:55           ` Luiz Augusto von Dentz
2011-09-13  6:39         ` Antti Julku [this message]
2011-09-13  8:48           ` Marcel Holtmann

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=4E6EFAAF.3050505@nokia.com \
    --to=antti.julku@nokia.com \
    --cc=claudio.takahasi@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).