From: Peter Stephenson <pws@csr.com>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Slaves in Sniff mode
Date: Wed, 23 Jun 2004 18:41:49 +0100 [thread overview]
Message-ID: <200406231741.i5NHfnqF022172@news01.csr.com> (raw)
In-Reply-To: "tOpSy TuRvY"'s message of "Wed, 23 Jun 2004 19:15:28 +0200." <Pine.BSO.4.58.0406231904480.29930@nemo.student.utwente.nl>
tOpSy TuRvY wrote:
> Assume that the communication is taking place between two PANUs (i.e.
> slaves) in a PAN, where the destination PANU is in sniff mode. From your
> answer, am I correct in concluding that:
>
> a) The fact that the receiving PANU is in sniff mode is transparent to the
> sender (except that the transfer rate will be lower and there may be some
> delays)
Yes, there's no reason the sender would notice apart from the data in
small bursts. (It's not like park mode where data isn't sent.)
> b) The queueing you mentioned will take place at the GN
So you're sending data PANU -> GN -> PANU? If both links are in sniff,
the most likely place for data to queue up is at the sending PANU. But
this is simply a question of available bandwidth, there's no specific
dependence on sniff. You'd get the same thing if, say, the link quality
was very poor, or you were using one of our competitors' devices :-).
> One last question on this issue. Can the GN in Bluez ask the PANU to go
> into sniff mode *automatically* based on some criteria (e.g. low
> activity), or ask it to come out of sniff mode (e.g. based on a large
> queue).
It would be up to the host code to do this. There's nothing stopping
(say) the bnep layer from monitoring data and sending sniff and unsniff
requests. There's no facility for doing this below HCI.
pws
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
www.mimesweeper.com
**********************************************************************
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-06-23 17:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1BcqIi-0002cT-53@sc8-sf-list2.sourceforge.net>
2004-06-22 18:57 ` [Bluez-users] Max Number of PANUs supported in PAN tOpSy TuRvY
2004-06-22 21:30 ` Marcel Holtmann
2004-06-22 22:07 ` tOpSy TuRvY
2004-06-22 22:14 ` Marcel Holtmann
2004-06-23 11:23 ` [Bluez-users] Slaves in Sniff mode tOpSy TuRvY
2004-06-23 12:06 ` Peter Stephenson
2004-06-23 12:16 ` Marcel Holtmann
2004-06-23 12:58 ` tOpSy TuRvY
2004-06-23 13:30 ` Marcel Holtmann
2004-06-23 16:06 ` Peter Stephenson
2004-06-23 16:33 ` Marcel Holtmann
2004-06-23 17:15 ` tOpSy TuRvY
2004-06-23 17:41 ` Peter Stephenson [this message]
2004-06-24 9:43 ` tOpSy TuRvY
2004-06-24 10:09 ` Peter Stephenson
2004-06-24 11:39 ` [Bluez-users] BT_ADDR Address Resolution tOpSy TuRvY
2004-06-24 12:06 ` Marcel Holtmann
2004-06-24 12:26 ` tOpSy TuRvY
2004-06-24 12:31 ` Marcel Holtmann
2004-06-24 12:46 ` tOpSy TuRvY
2004-06-24 12:54 ` Marcel Holtmann
2004-06-23 17:59 ` [Bluez-users] Slaves in Sniff mode 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=200406231741.i5NHfnqF022172@news01.csr.com \
--to=pws@csr.com \
--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