From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luis R. Rodriguez Date: Wed, 14 Oct 2009 15:28:56 -0700 Subject: [ath9k-devel] ath9k rate control - rc.c In-Reply-To: References: Message-ID: <20091014222856.GB19352@tux> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On Wed, Oct 14, 2009 at 03:10:10PM -0700, Rakesh Kumar wrote: > Is RSSI a parameter to rate control algorithm? I am not sure but it may be there for historical purposes. > It seems like it is > mantaining RSSI state and everything but when it comes to making the > decision of what rate to choose, it does that purely by maximizing > expected throughput which is a function of PER. Yeah from what I recall this is how it worked too, but Vasanth may know better. > Just curious, why the part of codes relating to RSSI maintenance > are there? Maybe ANI, I forget. > Do they represent change of directions during the development of rc.c code? I don't think I understand your question. > I apologize if this has been previously discussed on the list but who owns > the rc.c part of the ath9k code, in one of emails Louis had written that > he tries to stay away from it. :) Well I stay away from it because IMHO its pretty convoluted. But I should note that it was designed to be simple but more importantly to run really well on low end MIPS APs. Another reason I stay away is I believe minstrel can eventually be made MCS aware and it may work better. But someone has to work on that first. Luis