From: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Georgiewskiy Yuriy <bottleman@icf.org.ru>,
Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>,
devel@lists.open80211s.org, ath9k-devel@lists.ath9k.org,
linux-wireless@vger.kernel.org
Subject: Re: [ath9k-devel] improve operational ANI in Mesh mode
Date: Wed, 20 Feb 2013 11:31:20 +0100 [thread overview]
Message-ID: <20130220103120.GA431@pandem0nium> (raw)
In-Reply-To: <CAJ-VmomPkPvABSJtdb6Y=fDNxyd_XtE6sk9yWQzw9qC7rjkwiA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
Hey Adrian,
On Tue, Feb 19, 2013 at 08:31:25AM -0800, Adrian Chadd wrote:
> Well, ANI does adjust some of its parameters based on the beacon
> signal level. It uses that as an estimate for how "strong" the signal
> is likely to be and tunes the baseband to either be highly sensitive
> or slightly on the deafer side.
>
> If you have many sources of beacons (read: ibss, mesh, TDMA in my
> case) then that particular feature of ANI can't be used and it should
> be disabled. The code should be special casing it.
>
> I suggest someone writes a bunch of test functions:
>
> * whether we see no beacons (ie, AP mode)
> * whether we see one set of beacons (ie, STA mode)
> * whether we see multiple sets of beacons (ie ,everything else)
this sounds useful - and easier to maintain than checking each
IFTYPE seperately (we add iftypes after all ...).
Maybe Felix knows more about this? He has ported ANI as far as I know. :)
Cheers,
Simon
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2013-02-20 10:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 2:43 improve operational ANI in Mesh mode Georgiewskiy Yuriy
2013-02-16 4:08 ` Adrian Chadd
2013-02-16 4:18 ` Georgiewskiy Yuriy
2013-02-19 13:40 ` Simon Wunderlich
2013-02-19 14:04 ` Georgiewskiy Yuriy
2013-02-19 16:31 ` [ath9k-devel] " Adrian Chadd
2013-02-19 16:49 ` Georgiewskiy Yuriy
2013-02-19 17:20 ` Adrian Chadd
2013-02-19 18:29 ` Sujith Manoharan
2013-02-19 18:33 ` Adrian Chadd
2013-02-19 18:38 ` Georgiewskiy Yuriy
2013-02-19 18:44 ` Sujith Manoharan
2013-02-19 19:11 ` Georgiewskiy Yuriy
2013-02-19 19:37 ` Adrian Chadd
2013-02-19 20:31 ` Georgiewskiy Yuriy
2013-02-20 3:30 ` Yeoh Chun-Yeow
2013-02-20 19:31 ` Georgiewskiy Yuriy
2013-02-21 0:37 ` Georgiewskiy Yuriy
2013-02-21 1:08 ` Yeoh Chun-Yeow
2013-02-21 1:23 ` Georgiewskiy Yuriy
2013-02-20 14:24 ` Bob Copeland
2013-02-20 19:55 ` Georgiewskiy Yuriy
2013-02-20 20:25 ` Bob Copeland
2013-02-20 20:27 ` Bob Copeland
2013-02-20 3:12 ` Sujith Manoharan
2013-02-20 10:31 ` Simon Wunderlich [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=20130220103120.GA431@pandem0nium \
--to=simon.wunderlich@s2003.tu-chemnitz.de \
--cc=adrian@freebsd.org \
--cc=ath9k-devel@lists.ath9k.org \
--cc=bottleman@icf.org.ru \
--cc=devel@lists.open80211s.org \
--cc=linux-wireless@vger.kernel.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).