All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Derek Smithies <derek@indranet.co.nz>
Cc: Bruno Randolf <br1@einfach.org>,
	"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>,
	"linville@tuxdriver.com" <linville@tuxdriver.com>
Subject: Re: [ath5k-devel] [PATCH 00/10] ANI for ath5k
Date: Thu, 25 Mar 2010 14:13:11 -0700	[thread overview]
Message-ID: <20100325211311.GG7651@tux> (raw)
In-Reply-To: <alpine.DEB.2.00.1003261001530.24989@kauri.acheron.indranet.co.nz>

On Thu, Mar 25, 2010 at 02:10:55PM -0700, Derek Smithies wrote:
> Hi,
> On Thu, 25 Mar 2010, Bruno Randolf wrote:
> > This is ANI for ath5k.
> Fantastic!!
>   I have used your initial ani patch set here, and it did help througput 
> etc.
> >
> > - Improve beacon averaging algorithm for IBSS: Maybe we should keep track of
> >  the average RSSI on a per-node basis and use the minimum of those in order
> >  not to loose far away nodes? The other option would be to limit the
> >  parameters we control similar to AP mode.
> 
> We have talked about this before. I thought that we agreed 
> that adhoc nodes may
>    a)be activated at any time
>    b)be positioned at an unknown distance apart
> 
> it therefore makes no sense to average the RSSI over the current nodes.
> If all the current nodes in the network are close by, the ani algorithm 
> will wind the sensitivity down. Consequently, if a remote node is 
> started, it will not be able to connect. Yet, the remote node should 
> have been able to connect as the slot times etc were long enough, 
> and the link budget is fine...
> 
> So yes, the only way to 
> > - 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?

  Luis

  reply	other threads:[~2010-03-25 21:13 UTC|newest]

Thread overview: 27+ 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 [this message]
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: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
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=20100325211311.GG7651@tux \
    --to=lrodriguez@atheros.com \
    --cc=ath5k-devel@lists.ath5k.org \
    --cc=bob@bobcopeland.com \
    --cc=br1@einfach.org \
    --cc=derek@indranet.co.nz \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.