All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Javier Cardona <javier@cozybit.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	Luis Carlos Cobo <luisca@cozybit.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: sta_info->fail_avg
Date: Wed, 10 Sep 2008 22:24:58 -0700	[thread overview]
Message-ID: <20080911052458.GA24835@tesla> (raw)
In-Reply-To: <445f43ac0809102215w2637dff7sa2c60dd8c31ccf6@mail.gmail.com>

On Wed, Sep 10, 2008 at 10:15:12PM -0700, Javier Cardona wrote:
> Johannes,
> 
> On Wed, Sep 10, 2008 at 4:59 PM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
> > Hi Luis,
> >
> > Can you explain what you're using this for in the mesh code?
> 
> It is used to estimate the average retransmissions that will be
> required to send a nominal frame over a given peer link.
> That's one component of the airtime link metric.
> 
> > I do know that neither ath9k's nor Intel's rate
> > control algorithms ever set it so it'll always be zero.
> 
> In that case transmission failures will not be taken into account and
> nodes with that hardware will report a lower (better) link metric than
> what they should.  In other words, those nodes will attract mesh
> traffic, which will provide a strong incentive for the driver
> maintainers to set that value correctly :)

Neither of our drivers support Mesh yet though so this is good to know,
once we do add it (or someone does).

  Luis

  reply	other threads:[~2008-09-11  5:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-10 23:59 sta_info->fail_avg Johannes Berg
2008-09-11  5:15 ` sta_info->fail_avg Javier Cardona
2008-09-11  5:24   ` Luis R. Rodriguez [this message]
2008-09-11 10:54   ` sta_info->fail_avg 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=20080911052458.GA24835@tesla \
    --to=lrodriguez@atheros.com \
    --cc=javier@cozybit.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luisca@cozybit.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.