From: "Martín Ernesto Barreyro" <barreyromartin@gmail.com>
To: Hin-Tak Leung <hintak.leung@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: Changing from Minstrel to PID
Date: Mon, 09 Nov 2009 23:18:23 -0300 [thread overview]
Message-ID: <1257819503.13712.3.camel@localhost.localdomain> (raw)
In-Reply-To: <3ace41890911081538u1a6649eybdd38ffe4b0fd6fc@mail.gmail.com>
El dom, 08-11-2009 a las 23:38 +0000, Hin-Tak Leung escribió:
> On Sun, Nov 8, 2009 at 9:39 PM, Martín Ernesto Barreyro
> <barreyromartin@gmail.com> wrote:
>
> > I don't know, I'll post the minstrel statistics, maybe it'll help you.Some
> > months ago the rate control wasn't working at all, and Larry took care of
> > it. Since that both algorithms started working, the count of retrys was
> > missing at that time.
> > Both algorithms started working, but minstrel sometimes works for while but
> > then goes to the max rate, in my case 54mbps if i a don't change it to other
> > with iwconfig, e.g iwconfig wlan0 rate 11M auto
>
> I am sure somebody with more experience with tuning mistrel can give
> you some help...
>
> >> The other thing is, you can probably patch compat-wireless to do
> >> something similiar or at least experiment with it, as long as your
> >> kernel is configured with most of them as modules. Switching
> >> compat-wireless is quite easy, and particularly with the
> >> 'driver-select rtl818x' option you just rebuild about 6 kernel modules
> >> instead of the usual 50+, which makes it quite quick and painless.
> >
> >
> > You are saying that i could give it a try for adding the option that i was
> > asking for?
> > Iill give it a shot but i don't know how many time will it take me
>
> Yes, compat-wlreless is useful for trying out small patches. Adding a
> module parameter isn't too much trouble, i think - and there are
> plenty of examples (many kernel module do parameters).
I've my 2.31 kernel running (from archlinux repositories) and
compat-wireless 2009-11-06 and now not even with pid i get it working
good. It goes to the max rate available.
>From the distance that I'm from the AP i have to limit the rate to
11Mbps
I'll compile wireless testing and i'll post the statistics, or if
someone tell the information they need to debug it i'll post it.
--
Martín Ernesto Barreyro <barreyromartin@gmail.com>
Analista Universitario en Redes de Datos.
next prev parent reply other threads:[~2009-11-10 2:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 21:29 Changing from Minstrel to PID Martín Ernesto Barreyro
2009-11-06 21:48 ` John W. Linville
2009-11-06 22:13 ` Martín Ernesto Barreyro
2009-11-06 22:24 ` Bob Copeland
2009-11-06 22:40 ` Martín Ernesto Barreyro
2009-11-07 13:43 ` John W. Linville
2009-11-07 17:26 ` Bob Copeland
2009-11-06 23:01 ` Martín Ernesto Barreyro
2009-11-07 12:18 ` Hin-Tak Leung
[not found] ` <cec7b3dc0911081339g5f838527nf76a15889ecaddbd@mail.gmail.com>
2009-11-08 23:38 ` Hin-Tak Leung
2009-11-10 2:18 ` Martín Ernesto Barreyro [this message]
2009-11-07 13:42 ` John W. Linville
2009-11-09 12:11 ` Martín Ernesto Barreyro
2009-11-09 15:57 ` Hin-Tak Leung
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=1257819503.13712.3.camel@localhost.localdomain \
--to=barreyromartin@gmail.com \
--cc=hintak.leung@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 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).