public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] [Bluez Users] Page timeout during sdp on heavy	traffic.
Date: Wed, 30 May 2007 09:58:04 +0200	[thread overview]
Message-ID: <1180511884.21432.170.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <80236d750705300036v3409e6a7kcb58e9f746f6cac@mail.gmail.com>

Hi Emanuele,

> Maybe I was not clear sorry, the sdp search I do on hci1 is
> serialized. It's a thread started each one a new device is discovered.
> He does 1 sdp search and quit. Then another one is started on next
> device on the list of the discovered ones. 

please don't use the word threads if it has nothing to do with your
setup. It confuses people and it confuses me. It is a minor technical
detail.

> I know I cant do inquiry and page at same time but I read elsewhere on
> this forum that using 2 separate hci at once you can actually achieve
> that. But maybe I was wrong if so sorry for the silly question.
> Simply I do inquiry with hci0 (never stops) and each time it finds a
> group devices I start an sdp search on hci1 (1 device at time
> serialized) but as I wrote sometimes this request return page timeout
> while other time it works well as per the hcidump I attached on
> previous message. 
> At this time the inquiry is always running (not periodic inquiry
> simply a looped inquiry request)
> That's only to check what's happening on heavy traffic.

So in general that works perfectly fine. Having inquiry on one and
service discovery running on another dongle.

However there are some minor details that needs to taken into account.
The piconets you create with your service discovery need also to be
taken down and this will be done by kernel automatically. This might
interfere with the next page. A sdp_close() will close the SDP session,
but it might still take another 3 seconds or more before the kernel
finally terminates the piconet. Never underestimate this.

Also the name resolving will create a temporary piconet and thus a page
from a different device might fail.

Regards

Marcel



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2007-05-30  7:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29 16:11 [Bluez-users] [Bluez Users] Page timeout during sdp on heavy traffic Emanuele Novelli
2007-05-29 20:20 ` Marcel Holtmann
2007-05-30  7:36   ` Emanuele Novelli
2007-05-30  7:58     ` Marcel Holtmann [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=1180511884.21432.170.camel@aeonflux.holtmann.net \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    /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