linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Saravana <saravanad@posedge.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Clarification needed on Last Tx Rate statistic update
Date: Wed, 07 Nov 2012 14:31:40 +0530	[thread overview]
Message-ID: <509A2374.4060601@posedge.com> (raw)
In-Reply-To: <1352275534.9854.6.camel@jlt4.sipsolutions.net>

Hi Johannes,

Thanks for the clarification. So it seems the in the other case that you 
had mentioned, we can confirm that last_tx_rate is updated with 
inappropriate value.
So probably we could add another variable for the highest 
performing/probability rate and update it with the  txrc.reported rate 
value.
The Last_tx_rate update with the highest performing/probability rate can 
be removed.

As far as Last Tx Rate is concerned, should we need to check for the flag?
I think the Last Tx Rate can be updated irrespective of the 
IEEE80211_HW_HAS_RATE_CONTROL set or not.

Please let me know your inputs on this.

Thanks,
Saravana
On 11/07/2012 01:35 PM, Johannes Berg wrote:
> On Wed, 2012-11-07 at 13:17 +0530, Saravana wrote:
>
>> Could somebody clarify why the statistics update happens only when the
>> rate control is done by the hardware(flag IEEE80211_HW_HAS_RATE_CONTROL
>> is set)?
> In the other case, it's set to txrc.reported_rate upon transmission, so
> it's not the *last* rate, but more accurately the highest
> performing/probability rate.
>
> johannes
>
>


  reply	other threads:[~2012-11-07  9:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-07  7:47 Clarification needed on Last Tx Rate statistic update Saravana
2012-11-07  8:05 ` Johannes Berg
2012-11-07  9:01   ` Saravana [this message]
2012-11-08 14:11     ` Johannes Berg

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=509A2374.4060601@posedge.com \
    --to=saravanad@posedge.com \
    --cc=johannes@sipsolutions.net \
    --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).