From: Mattias Nissler <mattias.nissler@gmx.de>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
rt2400-devel <rt2400-devel@lists.sourceforge.net>,
linux-wireless <linux-wireless@vger.kernel.org>,
Stefano Brivio <stefano.brivio@polimi.it>
Subject: tx_status reporting of RTS/CTS frames
Date: Tue, 11 Dec 2007 23:42:02 +0100 [thread overview]
Message-ID: <1197412922.7030.11.camel@localhost> (raw)
Hi,
rt2x00 devices can't generate rts/cts frames themselves, but rely on the
driver to generate them. Also, the hardware reports tx status back for
those frames. Now the question is whether these frames should be
reported back to mac80211 using ieee80211_tx_status[_irqsafe]. AFAIK,
this has some subtle effects, e.g. they won't show up on monitor
interfaces if we don't report them.
I'd like to know the official policy. Cause if they are supposed to
reported, I need to filter them in the rate control algorithm. This is
to make sure the failed frames percentage count isn't biased for drivers
that report them compared to drivers that cannot.
Mattias
next reply other threads:[~2007-12-11 22:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 22:42 Mattias Nissler [this message]
2007-12-12 17:15 ` tx_status reporting of RTS/CTS frames Johannes Berg
2007-12-12 19:49 ` Mattias Nissler
2007-12-13 11:34 ` Johannes Berg
2007-12-13 18:56 ` Mattias Nissler
2007-12-13 19:14 ` Johannes Berg
2007-12-23 21:18 ` Ivo van Doorn
2007-12-14 5:20 ` Jouni Malinen
2007-12-14 12:10 ` Johannes Berg
2007-12-23 21:17 ` Ivo van Doorn
2007-12-23 21:29 ` Johannes Berg
2007-12-23 21:50 ` Ivo van Doorn
2007-12-23 21:54 ` Johannes Berg
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=1197412922.7030.11.camel@localhost \
--to=mattias.nissler@gmx.de \
--cc=ivdoorn@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=rt2400-devel@lists.sourceforge.net \
--cc=stefano.brivio@polimi.it \
/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).