From: Jean Tourrilhes <jt@hpl.hp.com>
To: Pavel Roskin <proski@gnu.org>
Cc: NetDev <netdev@vger.kernel.org>
Subject: Re: dBm cutoff at -1dBm is too low
Date: Fri, 5 May 2006 10:28:18 -0700 [thread overview]
Message-ID: <20060505172818.GA7543@bougret.hpl.hp.com> (raw)
In-Reply-To: <1146760665.5294.65.camel@dv>
On Thu, May 04, 2006 at 12:37:45PM -0400, Pavel Roskin wrote:
> Hello, Jean!
>
> I'm converting Orinoco to the dBm reporting, and it turns out that the
> best signal iwconfig will report is -1dBm (0.8mW). This would happen if
> qual->level has its highest value of 255. Please see this code from
> wireless_tools.29.pre10:
>
> len = snprintf(buffer, buflen, "Signal level%c%d dBm ",
> qual->updated & IW_QUAL_LEVEL_UPDATED ? '=' : ':',
> qual->level - 0x100);
Yes, that's correct.
Note that the main limitation is that before I introduced the
explicit IW_QUAL_DBM in WE-19, the way to know if the value was
relative or dBm was to use the 'sign' of it, i.e. value above 0 were
non-dBm. The test is a few line before this snipset :
---------------------------------------------------------
/* Check if the statistics are in dBm or relative */
if((qual->updated & IW_QUAL_DBM)
|| (qual->level > range->max_qual.level))
{
---------------------------------------------------------
There are still quite a few drivers which have not been
converted to use IW_QUAL_DBM, so I don't want to drop the backward
compatibility yet.
> With most cards transmitting at 100mW and some going as high as 500mW,
> it's not unreasonable to expect that the received signal may exceed 1mW
> for closely located receivers with good antennas. I have seen HostAP
> reporting as much as 3mW through the proc filesystem!
My rationale was two fold.
First, such high values are quite unlikely, because cards need
to be very close, which does not happen that often. Power is limited
by spec and power consumption, so unlikely to go higher than
this. Also, I'm surprised that the card receiver does not saturate
with such high receive power, but I would question the accuracy of the
measurement.
Second, the measurement is useful mostly in marginal
conditions. When signal is great, you don't really care, when signal
is low, you want to tweak your system to improve reception.
> Wouldn't it be better to put the cutoff at a higher value? The simplest
> approach would be to treat qual->level and qual->noise as signed char,
> which would put the cutoff and 127dBm. 500 gigawatts should be enough
> for everyone :-)
FCC says Tx 1W @ 2.4 GHz, ETSI says Tx 100mW @ 2.4 Gz. Yeah,
you could use directional antennas. So, realistically, we only need to
extend to +30dBm.
On the other hand, I expect that with MIMO and UWB we would
start to receive signal weaker than what we currently do, and you
don't want to cutoff the bottom of the range (is -128dBm enough ?).
I tried to use 'signed' in the struct a long while ago, and
for some reason it broke left and right, I don't remember the
details. So, whatever we do, it would not be straightforward.
> Regards,
> Pavel Roskin
Have fun...
Jean
next prev parent reply other threads:[~2006-05-05 17:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 16:37 dBm cutoff at -1dBm is too low Pavel Roskin
2006-05-05 17:28 ` Jean Tourrilhes [this message]
2006-05-07 3:32 ` Pavel Roskin
2006-05-08 17:17 ` Jean Tourrilhes
2006-05-09 4:54 ` Pavel Roskin
2006-05-09 18:54 ` Jean Tourrilhes
2006-05-08 3:35 ` Pavel Roskin
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=20060505172818.GA7543@bougret.hpl.hp.com \
--to=jt@hpl.hp.com \
--cc=netdev@vger.kernel.org \
--cc=proski@gnu.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).