From: Felix Fietkau <nbd@openwrt.org>
To: linux-wireless <linux-wireless@vger.kernel.org>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
Johannes Berg <johannes@sipsolutions.net>
Subject: [RFC 1/2] mac80211: add private driver flags and ampdu length to tx info
Date: Sat, 14 Nov 2009 01:48:01 +0100 [thread overview]
Message-ID: <4AFDFE41.9000003@openwrt.org> (raw)
Some drivers may want to store a few flags of their own in the tx
info. Also it is useful for 11n rate control to know the total number
of aggregated frames in an AMPDU, not just the ones that were acked.
Use two previously unused padding bytes to store those two values
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
---
--- a/include/net/mac80211.h
+++ b/include/net/mac80211.h
@@ -386,6 +386,7 @@ struct ieee80211_tx_rate {
* @flags: transmit info flags, defined above
* @band: the band to transmit on (use for checking for races)
* @antenna_sel_tx: antenna to use, 0 for automatic diversity
+ * @driver_flags: flags for internal driver use
* @pad: padding, ignore
* @control: union for control data
* @status: union for status data
@@ -404,7 +405,8 @@ struct ieee80211_tx_info {
u8 antenna_sel_tx;
/* 2 byte hole */
- u8 pad[2];
+ u8 driver_flags;
+ u8 ampdu_len;
union {
struct {
next reply other threads:[~2009-11-14 0:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-14 0:48 Felix Fietkau [this message]
2009-11-14 0:51 ` [RFC 2/2] ath9k: get rid of tx_info_priv Felix Fietkau
2009-11-14 2:06 ` Luis R. Rodriguez
2009-11-14 2:08 ` Luis R. Rodriguez
2009-11-14 9:31 ` [RFC 1/2] mac80211: add private driver flags and ampdu length to tx info Johannes Berg
2009-11-14 10:40 ` Ivo Van Doorn
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=4AFDFE41.9000003@openwrt.org \
--to=nbd@openwrt.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.