From: Jouni Malinen <j@w1.fi>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>,
Zhu Yi <yi.zhu@intel.com>, Tomas Winkler <tomasw@gmail.com>,
Tomas Winkler <tomas.winkler@intel.com>,
Nick Kossifidis <mickflemm@gmail.com>,
"Luis R. Rodriguez" <lrodriguez@atheros.com>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
Felix Fietkau <nbd@openwrt.org>
Subject: Re: [PATCH 0/5] mac80211, iwlwifi, ath9k: Fix rate scaling for IEEE80211_TX_CTL_NO_ACK packets
Date: Thu, 23 Apr 2009 21:09:28 +0300 [thread overview]
Message-ID: <20090423180928.GA22426@jm.kir.nu> (raw)
In-Reply-To: <69e28c910904231035u7ff2d9bbnbf1a74ece718659@mail.gmail.com>
On Thu, Apr 23, 2009 at 07:35:55PM +0200, G=C3=A1bor Stefanik wrote:
> Handling of multicast/NO_ACK packets by mac80211 rate scaling is a
> mess. Basically, the rule of thumb is that any packet with
> IEEE80211_TX_CTL_NO_ACK (including multicasts and broadcasts, which
> always have this flag set) should be sent at lowest rate (unless
> overridden by radiotap - this is not covered in this patchset), with
> no retries.
While this may be the case with the current rate control
implementations, this is not a good assumption to make.
Multicast/broadcast frames could (and often really should) be
transmitted at higher rate, i.e., the rate control algorithm could
figure out that all associated STAs should be able to receive frames at
a higher basic rate.
As far as unicast no-ACK frames are concerned, those could (and again,
should) be sent at higher rate, too, if the receiving STA can be assume=
d
to be able to receive the frame with "large enough" probability.
> So, the right thing to do in any rate scaling algorithm:
> * Check for IEEE80211_TX_CTL_NO_ACK. No need to check
> is_multicast_ether_addr, as multicasts always have NO_ACK set.
> * If it is set, select the lowest available rate (unless overridden
> by radiotap), with a retry count of 0 (total try count of 1).
I would not agree with these as general rules for all rate control
algorithms.
--=20
Jouni Malinen PGP id EFC895F=
A
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-04-23 18:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 17:35 [PATCH 0/5] mac80211, iwlwifi, ath9k: Fix rate scaling for IEEE80211_TX_CTL_NO_ACK packets Gábor Stefanik
2009-04-23 18:09 ` Jouni Malinen [this message]
2009-04-23 18:18 ` Gábor Stefanik
2009-04-24 17:31 ` Felix Fietkau
2009-04-25 7:12 ` Johannes Berg
2009-04-28 20:53 ` Gábor Stefanik
2009-04-30 18:28 ` John W. Linville
2009-04-30 19:02 ` John W. Linville
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=20090423180928.GA22426@jm.kir.nu \
--to=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=mcgrof@gmail.com \
--cc=mickflemm@gmail.com \
--cc=nbd@openwrt.org \
--cc=netrolller.3d@gmail.com \
--cc=tomas.winkler@intel.com \
--cc=tomasw@gmail.com \
--cc=yi.zhu@intel.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).