From: Johannes Berg <johannes@sipsolutions.net>
To: Michael Wu <flamingice@sourmilk.net>
Cc: Claudio Matsuoka <claudio@mandriva.com>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: RTL8187 rate control problems
Date: Wed, 07 Nov 2007 15:20:43 +0100 [thread overview]
Message-ID: <1194445243.4470.25.camel@johannes.berg> (raw)
In-Reply-To: <200711061947.21927.flamingice@sourmilk.net> (sfid-20071107_005157_014757_0E6753FD)
[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]
> There's no easy way to do tx ack reporting on the rtl8187.
This also means it doesn't show you outgoing frames on a monitor. We
really need to find a solution here that takes into account our current
use of tx status reports for outgoing frame monitor as well as rate
control.
At the higher network speeds of 802.11n equipment we'll not want to do
this anyway.
Since hostapd needs to know whether the packets it sent were acked,
we'll have to go back to using IEEE80211_TXCTL_REQ_TX_STATUS for those
injected frames.
Then we need to decide whether we want to report all outgoing frames on
monitor interfaces or only those where the hardware was able to provide
a status report. The latter would be sufficient for hostapd, of course.
Finally, we need to create a new hardware flag that determines whether
the driver will report status for all frames or not, this influences the
possible rate control algorithm choices. Of course we still need to
write rate control algorithms that are able to work with synthesized
information...
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2007-11-07 15:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 15:23 RTL8187 rate control problems Claudio Matsuoka
2007-11-06 16:41 ` John W. Linville
2007-11-06 16:47 ` John W. Linville
2007-11-06 18:37 ` Michael Wu
2007-11-07 0:39 ` Claudio Matsuoka
2007-11-07 0:47 ` Michael Wu
2007-11-07 14:20 ` Johannes Berg [this message]
2007-11-09 11:13 ` Claudio Matsuoka
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=1194445243.4470.25.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=claudio@mandriva.com \
--cc=flamingice@sourmilk.net \
--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).