From: Johannes Berg <johannes@sipsolutions.net>
To: Helmut Schaa <helmut.schaa@googlemail.com>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com
Subject: Re: [PATCH] mac80211: Populate radiotap header with MCS info for tx'ed frames
Date: Tue, 11 Oct 2011 13:51:15 +0200 [thread overview]
Message-ID: <1318333875.3965.10.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <CAGXE3d8cuBg28PfMYQcAJ96oTEqUg6rG8ExUr+Sezq51eM2J_Q@mail.gmail.com> (sfid-20111011_134834_133793_0F4839D3)
On Tue, 2011-10-11 at 13:48 +0200, Helmut Schaa wrote:
> On Tue, Oct 11, 2011 at 1:35 PM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
> > So using something like
> > this would allow us to save some space as well:
> >
> > struct ieee80211_tx_status_rtap_hdr {
> > struct ieee80211_radiotap_header hdr;
> > union {
> > struct {
> > u8 rate;
> > u8 padding_for_rate;
> > __le16 tx_flags;
> > u8 data_retries;
> > } non_mcs;
> > struct {
> > __le16 tx_flags;
> > u8 data_retries;
> > u8 mcs_known, mcs_flags, mcs;
> > } mcs;
> > }
> > } __packed;
>
> I thought about the same but this means we have to fill in
> different fields (non_mcs.tx_flags vs mcs.tx_flags) for the MCS
> vs legacy path and set the radiotap header len differently in
> both cases.
Good point.
> Or should we just get rid of the whole struct and fill in the
> rtap header dynamically like it is done in the rx path and
> drop the build-bug-on thing?
I wouldn't mind that either, but we'll want to have a WARN_ON_ONCE()
somewhere if we run out of space.
johannes
next prev parent reply other threads:[~2011-10-11 11:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 11:28 [PATCH] mac80211: Populate radiotap header with MCS info for tx'ed frames Helmut Schaa
2011-10-11 11:35 ` Johannes Berg
2011-10-11 11:48 ` Helmut Schaa
2011-10-11 11:51 ` Johannes Berg [this message]
2011-10-11 11:52 ` Helmut Schaa
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=1318333875.3965.10.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=helmut.schaa@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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