linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bruno Randolf <br1@einfach.org>
To: Derek Smithies <derek@indranet.co.nz>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
	"bob@bobcopeland.com" <bob@bobcopeland.com>,
	"ath5k-devel@lists.ath5k.org" <ath5k-devel@lists.ath5k.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [ath5k-devel] [PATCH 00/10] ANI for ath5k
Date: Fri, 26 Mar 2010 10:46:10 +0900	[thread overview]
Message-ID: <201003261046.10755.br1@einfach.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1003261416120.24989@kauri.acheron.indranet.co.nz>

On Friday 26 March 2010 10:21:50 Derek Smithies wrote:
> On Fri, 26 Mar 2010, Bruno Randolf wrote:
> >>>> - Improve beacon averaging algorithm for IBSS:
> >>> is to turn ani off. which means the issue you raised else where of
> >>> providing reasonable userland controls (not via debugfs) becomes
> >>> important.
> >> 
> >> If ANI helps IBSS so much then why not just default to turning it
> >> off within the driver?
> > 
> > i would say in most standard cases, IBSS nodes are close together or at a
> > similar distance, so it does make sense to use ANI by default.
> 
> Nope - I disagree. You have made a dangerous assumption, to asume
> that
>    IBSS node are close together or at a similar distance
>
> if you have a network of ibss nodes, and then look at the rate tables of
> the different nodes (minstrel is great here - it gives a fair and accurte
> represetation of the best rate possible to other nodes) 

yeah, we all know how great minstrel is... really.

> you see there is
> some variation in the optimal rates between nodes.Which suggests that
> using some automatic ani algorithm in an ibss network will foreever lower
> performance for those nodes at the edge of the network.
> 
> > as well, we all agree that there should be userland controls. the
> > questions is just about the interface to use.
> 
> Definately - need userland controls. The default for IBSS should have
> ANI off. If the user wants to "futz" with it, they can. With ANI off for
> IBSS, you ensure that on startup, the network has the greatest chance of
> working.

i said in most *standard* cases - the standard case for IBSS is still 3 or 5 
guys sitting in a room, or close by, wanting to exchange some data. we should 
have good performance for that, therefore ANI on by default.

in larger IBSS mesh networks or outdoor deployments you will want to tune ANI 
manually anyhow, then you can turn it off.

again - i'm not willing to discuss this based on guesses and assumptions. 
looking at the rate tables will not tell you if using ANI will shut a node out 
or not. if you have test results showing that a specific ANI setting actually 
prevented a node from joining an IBSS, i'm happy to resume this discussion.

bruno

  parent reply	other threads:[~2010-03-26  1:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25  5:48 [PATCH 00/10] ANI for ath5k Bruno Randolf
2010-03-25  5:49 ` [PATCH 01/10] ath5k: remove static calibration interval variable Bruno Randolf
2010-03-25  5:49 ` [PATCH 02/10] ath5k: remove the use of SWI interrupt Bruno Randolf
2010-03-25  5:49 ` [PATCH 03/10] ath5k: optimize ath5k_hw_calibration_poll Bruno Randolf
2010-03-25  5:49 ` [PATCH 04/10] ath5k: move ath5k_hw_calibration_poll to base.c Bruno Randolf
2010-03-25  5:49 ` [PATCH 05/10] ath5k: keep beacon RSSI average Bruno Randolf
2010-03-25  5:49 ` [PATCH 06/10] ath5k: initialize default noise floor Bruno Randolf
2010-03-25  5:49 ` [PATCH 07/10] ath5k: simplify MIB counters Bruno Randolf
2010-03-25  5:49 ` [PATCH 08/10] ath5k: update phy errors codes Bruno Randolf
2010-03-25  5:49 ` [PATCH 09/10] ath5k: add capability flag for phyerror counters Bruno Randolf
2010-03-25  5:49 ` [PATCH 10/10] ath5k: Adaptive Noise Immunity (ANI) Implementation Bruno Randolf
2010-03-25 10:59   ` Joerg Pommnitz
2010-03-26  0:18     ` Bruno Randolf
2010-03-29  2:02   ` [ath5k-devel] " Bob Copeland
2010-03-29  2:26     ` Bruno Randolf
2010-03-25 21:10 ` [ath5k-devel] [PATCH 00/10] ANI for ath5k Derek Smithies
2010-03-25 21:13   ` Luis R. Rodriguez
2010-03-26  0:27     ` Bruno Randolf
2010-03-26  0:44       ` Luis R. Rodriguez
2010-03-26  0:53         ` Bruno Randolf
2010-03-26  1:06           ` Luis R. Rodriguez
2010-03-26  1:21       ` Derek Smithies
2010-03-26  1:32         ` Luis R. Rodriguez
2010-03-26  1:46         ` Bruno Randolf [this message]
2010-03-26 20:34           ` Derek Smithies
2010-03-27  5:18             ` Bruno Randolf

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=201003261046.10755.br1@einfach.org \
    --to=br1@einfach.org \
    --cc=ath5k-devel@lists.ath5k.org \
    --cc=bob@bobcopeland.com \
    --cc=derek@indranet.co.nz \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lrodriguez@atheros.com \
    /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).