From: Helmut Schaa <helmut.schaa@googlemail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Felix Fietkau <nbd@openwrt.org>,
Ivo van Doorn <ivdoorn@gmail.com>,
Gertjan van Wingerde <gwingerde@gmail.com>,
linux-wireless@vger.kernel.org
Subject: Re: rt2800, minstrel_ht & mac80211
Date: Fri, 4 Jun 2010 12:32:53 +0200 [thread overview]
Message-ID: <201006041232.53326.helmut.schaa@googlemail.com> (raw)
In-Reply-To: <1275647301.9953.20.camel@jlt3.sipsolutions.net>
Am Freitag 04 Juni 2010 schrieb Johannes Berg:
> On Fri, 2010-06-04 at 12:22 +0200, Helmut Schaa wrote:
>
> > This meant that minstrel most of the time selected MCS15 as tx rate which
> > resulted in a huge number of retries and thus a very slow throughput.
> >
> > status.c:
> >
> > 178 /* the HW cannot have attempted that rate */
> > 179 if (i >= hw->max_rates) {
> > 180 info->status.rates[i].idx = -1;
> > 181 info->status.rates[i].count = 0;
> >
> > Johannes, is there a valid reason for this check in status.c. Can we remove
> > it without breaking anything else?
>
> IIRC there were/are some drivers that were not terminating the rates[]
> array correctly with a -1, thus this code.
Understood, so it's a driver workaround ;)
Maybe we should check which driver doesn't set it and fix these?
> > What other options would we have to fix this issue? Just use max_rates = 4
> > in rt2800 even if we will only use the first rate provided by minstrel and
> > then fall back to the global fallback setup (I tried that already and it
> > works just fine but seems not correct to me)?
>
> p54 kinda does some trickery in this area too, not really sure what to
> do though.
Thanks for the pointer, p54 just sets max_rates=4 even if it cannot support
it.
So, if you would like to keep the check I'll just use max_rates=4 in rt2800.
Helmut
prev parent reply other threads:[~2010-06-04 10:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 10:22 rt2800, minstrel_ht & mac80211 Helmut Schaa
2010-06-04 10:28 ` Johannes Berg
2010-06-04 10:32 ` Helmut Schaa [this message]
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=201006041232.53326.helmut.schaa@googlemail.com \
--to=helmut.schaa@googlemail.com \
--cc=gwingerde@gmail.com \
--cc=ivdoorn@gmail.com \
--cc=johannes@sipsolutions.net \
--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).