From: "Martín Ernesto Barreyro" <barreyromartin@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Re: rate instability in wireless stack
Date: Wed, 07 Jan 2009 04:46:53 -0200 [thread overview]
Message-ID: <1231310813.23835.1.camel@note-tatin> (raw)
Hello, I've rtl8187 usb wifi card on board (at less is inside my laptop=
)
and
I've some problems with the rate control.
When I use the PID algorithm with 2.6.26-1-686(debian) or 2.6.28 kernel=
s
or
minstrel with 2.6.28 it always goes to 54Mb/s, and it doesn't work. If =
I
run
iwconfig wlan0 rate 11M auto, it starts working. Its a little
"optimistic".
This is the rc_stats output
rate throughput ewma prob this prob this succ/attempt success
attempts
P 1 0.9 99.9 100.0 0( 0) 382
382
2 1.9 99.9 100.0 0( 0) 222
222
5.5 5.0 99.9 100.0 0( 0) 222
222
11 9.5 99.9 100.0 4( 4) 48070
48070
6 1.4 25.0 100.0 0( 0) 1
1
9 3.6 43.7 100.0 0( 0) 2
2
t 12 11.0 99.9 100.0 0( 0) 228
228
18 4.0 25.0 100.0 0( 0) 1
1
24 5.3 25.0 100.0 0( 0) 1
1
36 7.6 25.0 100.0 0( 0) 1
1
48 9.7 25.0 100.0 0( 0) 1
1
T 54 20.0 99.9 100.0 0( 0) 53
53
Total packet count:: ideal 8384 lookaround 441
All the attemps succeed, this is after I use iwconfig wlan0 rate 11M
auto,
otherwhise I couldn't write this, couse it stays at 54Mb/s and doesn't
works.
Today, january 7, I updated the driver with the compat-wireless tarball=
=2E
Now the
driver just stays in 1Mb/s.
rate throughput ewma prob this prob this succ/attempt success
attempts
TtP 1 0.0 0.0 0.0 1( 0) 0
0
2 0.0 0.0 0.0 0( 0) 0
0
5.5 0.0 0.0 0.0 0( 0) 0
0
11 0.0 0.0 0.0 0( 0) 0
0
6 0.0 0.0 0.0 0( 0) 0
0
9 0.0 0.0 0.0 0( 0) 0
0
12 0.0 0.0 0.0 0( 0) 0
0
18 0.0 0.0 0.0 0( 0) 0
0
24 0.0 0.0 0.0 0( 0) 0
0
36 0.0 0.0 0.0 0( 0) 0
0
48 0.0 0.0 0.0 0( 0) 0
0
54 0.0 0.0 0.0 0( 0) 0
0
Total packet count:: ideal 3546 lookaround 186
I send this problem to Larry, but since someone posted something simila=
r
I
thought it would be useful.
Mart=C3=ADn
--=20
Mart=C3=ADn Ernesto Barreyro <barreyromartin@gmail.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2009-01-07 6:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 6:46 Martín Ernesto Barreyro [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-04 16:46 rate instability in wireless stack Andi Kleen
2009-01-04 16:36 ` Michael Buesch
2009-01-04 17:41 ` Andi Kleen
2009-01-05 0:29 ` Larry Finger
2009-01-05 2:53 ` Andi Kleen
2009-01-05 3:55 ` Larry Finger
2009-01-05 5:02 ` Andi Kleen
2009-01-05 4:59 ` Larry Finger
2009-01-05 5:48 ` Andi Kleen
2009-01-05 5:51 ` Larry Finger
2009-01-05 8:17 ` Johannes Berg
2009-01-05 12:54 ` Andi Kleen
2009-01-05 13:32 ` Felix Fietkau
2009-01-05 14:23 ` Andi Kleen
2009-01-05 14:41 ` Felix Fietkau
2009-01-05 15:24 ` Andi Kleen
2009-01-05 15:25 ` Felix Fietkau
2009-01-05 16:35 ` Andi Kleen
2009-01-05 16:36 ` Felix Fietkau
2009-01-05 17:11 ` Andi Kleen
2009-01-05 17:01 ` Felix Fietkau
2009-01-05 19:33 ` Hin-Tak Leung
2009-01-05 20:16 ` Larry Finger
2009-01-05 4:22 ` Larry Finger
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=1231310813.23835.1.camel@note-tatin \
--to=barreyromartin@gmail.com \
--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 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.