Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Linux Wireless <linux-wireless@vger.kernel.org>
Subject: basic rate set / response frame rate
Date: Thu, 26 Jun 2008 22:18:30 +0200	[thread overview]
Message-ID: <1214511510.3783.44.camel@johannes.berg> (raw)

[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]

Hi,

How does hardware currently handle the control response (ACK/CTS) frame
rate? In 802.11 clause 9.6 talks about this, and we implement basic rate
handling in mac80211 to calculate the control response duration, but we
never tell drivers what bitrate to transmit control response frames at.

I suspect this is broken in all drivers (except maybe iwlwifi which
probably does it all in firmware.) The problem then is that if the AP
has basic rates higher than your firmware/hardware default, the control
response takes too long and the NAV isn't updated correctly in other
STAs.

How should we fix this?

The most straight-forward way would be to include a map of rate -> basic
rate into ieee80211_bss_conf, but that isn't easy because the size of
the map isn't known.

Another way would be to just give the driver the basic rate set, but
that means it has to calculate the mapping itself, subject to all the
rules in 802.11 clause 9.6.

Therefore, I prefer the former way, or giving the driver a function to
call for each rate on bss_info_changed to calculate the mapping.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

                 reply	other threads:[~2008-06-26 20:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1214511510.3783.44.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox