Linux wireless drivers development
 help / color / mirror / Atom feed
From: Jouni Malinen <j@w1.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Daniel Drake <dsd@gentoo.org>, Felix Fietkau <nbd@openwrt.org>
Subject: Re: [RFC] mac80211: fix short preamble determination
Date: Mon, 13 Oct 2008 18:59:38 +0300	[thread overview]
Message-ID: <20081013155938.GA30095@jm.kir.nu> (raw)
In-Reply-To: <1223713593.29811.38.camel@johannes.berg>

On Sat, Oct 11, 2008 at 10:26:33AM +0200, Johannes Berg wrote:
> When looking at this code during the rate control API rewrite
> yesterday, we wondered whether the determination of short
> preamble was correct or not. I don't think it was, and this
> should be better.

> -	if (ieee80211_is_data(hdr->frame_control) &&
> -	    tx->sdata->vif.bss_conf.use_short_preamble &&
> -	    (!tx->sta || test_sta_flags(tx->sta, WLAN_STA_SHORT_PREAMBLE)))
> +	if (tx->sdata->vif.bss_conf.use_short_preamble &&
> +	    (ieee80211_is_data(hdr->frame_control) ||
> +	     (tx->sta && test_sta_flags(tx->sta, WLAN_STA_SHORT_PREAMBLE)))

Changing '!tx->sta ||' to 'tx->sta &&' sounds reasonable, but I'm not so
sure about the other change.. In theory, short preamble is negotiated
per STA and while we do current disable short preamble completely in the
BSS if a non-short-preamble-capable STA associates, I'm not sure whether
that would be an absolute requirement. As far as management frames
(e.g., Probe Response) are concerned, IEEE 802.11-2007 18.2.2.2 has an
interesting statement: "all management traffic is returned with the same
type preamble as received". I have not been able to find normative
requirement for that being the case, though.

-- 
Jouni Malinen                                            PGP id EFC895FA

  reply	other threads:[~2008-10-13 16:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-11  8:26 [RFC] mac80211: fix short preamble determination Johannes Berg
2008-10-13 15:59 ` Jouni Malinen [this message]
2008-10-13 17:31   ` Johannes Berg
2008-10-13 17:54     ` Jouni Malinen
2008-10-13 18:03       ` Johannes Berg
2008-10-13 18:11         ` Jouni Malinen

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=20081013155938.GA30095@jm.kir.nu \
    --to=j@w1.fi \
    --cc=dsd@gentoo.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbd@openwrt.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