linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefano Brivio <stefano.brivio@polimi.it>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: "Luis R. Rodriguez" <mcgrof@winlab.rutgers.edu>,
	Michael Wu <flamingice@sourmilk.net>,
	linux-kernel@vger.kernel.org,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: rtl8187 rate control doesn't work
Date: Sat, 12 Jan 2008 20:28:54 +0100	[thread overview]
Message-ID: <20080112202854.2c24ba19@morte> (raw)
In-Reply-To: <478905B9.3080004@hauke-m.de>

On Sat, 12 Jan 2008 19:23:53 +0100
Hauke Mehrtens <hauke@hauke-m.de> wrote:

> I have tried wireless-2.6 and I have the same problem. If the rate goes
> over 11M no TCP/IP traffic goes through the wireless connecting. If rate
> is set to auto and the rate control algorithm changes it to something
> less than 11M TCP/IP traffic goes through, but if it is more than 11M no
> TCP/IP traffic goes through the wireless link.

And this is a problem if the rate control algorithm often sets the rate to
more than 11M even if connection is unreliable at that rate. Does this
actually happen? Are you currently using 'pid'?

Also, it would be fine to have a dump of the PID events. In order to get
this, you need to:
- build a kernel with debugfs enabled;
- mount debugfs (mount -t debugfs foo /mnt/debug)

Then, before testing:
cat /mnt/debug/ieee80211/phy0/stations/*/rc_pid_events > events_dump

You can even make a graph out of that, with a python script which Mattias
posted on this list some time ago, but a dump would be just fine.


--
Ciao
Stefano

  reply	other threads:[~2008-01-12 19:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <477F9890.5050107@hauke-m.de>
2008-01-05 21:54 ` rtl8187 rate control doesn't work Luis R. Rodriguez
2008-01-07 16:02   ` Hauke Mehrtens
2008-01-07 17:42     ` Luis R. Rodriguez
2008-01-11 22:39       ` Hauke Mehrtens
2008-01-12 14:44         ` Hauke Mehrtens
2008-01-12 15:21           ` Stefano Brivio
2008-01-12 18:23             ` Hauke Mehrtens
2008-01-12 19:28               ` Stefano Brivio [this message]
     [not found]                 ` <478F8CFF.2060105@hauke-m.de>
     [not found]                   ` <20080118210452.50c84d13@morte>
     [not found]                     ` <479109B7.5030808@hauke-m.de>
2008-01-18 20:26                       ` Stefano Brivio
2008-01-14 19:26         ` Luis R. Rodriguez

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=20080112202854.2c24ba19@morte \
    --to=stefano.brivio@polimi.it \
    --cc=flamingice@sourmilk.net \
    --cc=hauke@hauke-m.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@winlab.rutgers.edu \
    /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).