linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bruno Randolf <br1@einfach.org>
To: Jonathan Guerin <jonathan@guerin.id.au>
Cc: "linux-wireless" <linux-wireless@vger.kernel.org>,
	"ath5k-devel" <ath5k-devel@lists.ath5k.org>,
	nbd@openwrt.org
Subject: Re: ath5k: Weird Retransmission Behaviour
Date: Tue, 7 Dec 2010 11:34:27 +0900	[thread overview]
Message-ID: <201012071134.27162.br1@einfach.org> (raw)
In-Reply-To: <AANLkTi=Cg2GyRXz6a3Sv8X9ATXJLTSXgfEn+wU4NT0XP@mail.gmail.com>

On Tue December 7 2010 10:12:18 Jonathan Guerin wrote:
> > Another thing that strikes me here is: why use multi rate retries if the
> > rate is all the same? (Ignore the actual value of the rate, this is the
> > HW rate code).
> > 
> > Other examples:
> > 
> > *** txdesc tries 2
> > *** mrr 0 tries 9 rate 12
> > *** mrr 1 tries 2 rate 13
> > *** mrr 2 tries 3 rate 11
> > 
> > = 16 transmissions in sum.
> > 
> > *** txdesc tries 9
> > *** mrr 0 tries 3 rate 11
> > *** mrr 1 tries 9 rate 8
> > *** mrr 2 tries 3 rate 11
> > 
> > = 24 transmissions in sum. Again, rate[1] and rate[3] are the same, so
> > why bother setting it up twice?
> 
> I'm not sure if you still had a fixed rate set here - and I don't know
> 100% how minstrel works - but it could be that minstrel is trying to
> do some probing for better rates (if it was set to auto-rate)?

I did not set a fixed rate, so minstrel was probing for better rates / 
providing alternative rates.

In any case there is no reason to use the same rate twice.

bruno

  reply	other threads:[~2010-12-07  2:34 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-06  6:30 ath5k: Weird Retransmission Behaviour Jonathan Guerin
2010-12-06  8:14 ` Bruno Randolf
2010-12-06  9:36   ` [ath5k-devel] " Nick Kossifidis
2010-12-06 10:53     ` Sedat Dilek
2010-12-07  2:29       ` Bruno Randolf
2010-12-07  1:17     ` Jonathan Guerin
2010-12-08  8:06       ` Bruno Randolf
2010-12-08  8:12         ` Jonathan Guerin
2010-12-06 18:01   ` Björn Smedman
2010-12-07  1:19     ` Jonathan Guerin
2010-12-07  1:12   ` Jonathan Guerin
2010-12-07  2:34     ` Bruno Randolf [this message]
2010-12-08 16:08   ` Bob Copeland
2010-12-08 16:45     ` Bob Copeland
2010-12-08 16:56       ` John W. Linville
2010-12-08 17:06         ` Bob Copeland
2010-12-08 17:11           ` Bob Copeland
2010-12-08 17:50             ` Sedat Dilek
2010-12-08 21:36               ` Bob Copeland
2010-12-08 21:53     ` Jonathan Guerin
2010-12-09  9:21       ` Helmut Schaa
2010-12-09 12:38         ` Bob Copeland
2010-12-09 14:34           ` Jonathan Guerin
2010-12-09 17:00             ` Bob Copeland
2010-12-09 22:41               ` Jonathan Guerin
2010-12-06  9:38 ` Nick Kossifidis
2010-12-07  1:18   ` Jonathan Guerin

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=201012071134.27162.br1@einfach.org \
    --to=br1@einfach.org \
    --cc=ath5k-devel@lists.ath5k.org \
    --cc=jonathan@guerin.id.au \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbd@openwrt.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).