From: Johannes Berg <johannes@sipsolutions.net>
To: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Cc: linux-wireless@vger.kernel.org, j@w1.fi
Subject: Re: [PATCH 4/4] nl80211: add VHT support for set_bitrate_mask
Date: Wed, 04 Dec 2013 09:27:15 +0100 [thread overview]
Message-ID: <1386145635.4284.10.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CALhHN=q63LmZb7CvO=4sDWf70-O7_vc7T6jhU7gFQNtsH7PuDQ@mail.gmail.com> (sfid-20131203_172122_770299_EE929FB5)
On Tue, 2013-12-03 at 17:21 +0100, Janusz Dziedzic wrote:
> We need this for test purpose. Need to test different MCS/NSS
> configurations using our HW (mainly for VHT).
> Our HW supports setting TX fixed_rate for legacy/HT/VHT.
> So, we decided to use set_tx_bitrate_mask() as the best interface for
> that in nl80211.
> And after that we realize VHT implementation/change will be needed in
> nl80211/iw also.
> Because of that I send this VHT patch.
> So, we need this :)
Fair enough - please add a line or two to the commit log.
> >> +#define NL80211_MAX_SUPP_VHT_RATES 80
> >
> > Where does 80 come from? That seems odd?
> >
> NSS_MAX (8) * MCS_MAX (10)
>
> Eg.
> 9 - NSS=1, MCS=9
> 10 - NSS=2, MCS=0
> 11 - NSS=2, MCS=1
> ...
Can we please find a better way to encode this?
> >> + * @NL80211_TXRATE_VHT_MCS: VHT (MCS) rates allowed for TX rate selection
> >> + * in an array of MCS numbers.
> >
> > VHT has no "MCS numbers", so this doesn't make much sense?
> >
> You mean description only or mcs mask for vht (like above)?
Well, for VHT, there's no single "MCS" identifier for a rate, rates are
identified using MCS (0-9) and NSS (1-8). In mac80211, we do some bit
tricks to fit them into a single byte, but I see no reason to do this in
the nl80211 API and would rather have an API that makes this obvious.
The easiest would be using a struct, but then you don't need 80 bytes,
only 8 bitmaps (one for each NSS), for example.
johannes
next prev parent reply other threads:[~2013-12-04 8:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 8:50 [PATCH 1/4] nl80211: don't clear bitrate_mask twice Janusz Dziedzic
2013-12-03 8:50 ` [PATCH 2/4] nl80211: back to default bitrate_mask correctly Janusz Dziedzic
2013-12-03 14:20 ` Johannes Berg
2013-12-03 16:00 ` Janusz Dziedzic
2013-12-04 8:24 ` Johannes Berg
2013-12-03 8:50 ` [PATCH 3/4] nl80211/cfg80211: bitrate_mask, rename mcs to ht_mcs Janusz Dziedzic
2013-12-03 8:50 ` [PATCH 4/4] nl80211: add VHT support for set_bitrate_mask Janusz Dziedzic
2013-12-03 14:24 ` Johannes Berg
2013-12-03 16:21 ` Janusz Dziedzic
2013-12-04 8:27 ` Johannes Berg [this message]
2013-12-04 9:08 ` Janusz Dziedzic
2013-12-04 9:14 ` Johannes Berg
2013-12-03 8:50 ` [PATCH] iw: add VHT MCS set support to set bitrates Janusz Dziedzic
2013-12-03 14:20 ` [PATCH 1/4] nl80211: don't clear bitrate_mask twice Johannes Berg
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=1386145635.4284.10.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=j@w1.fi \
--cc=janusz.dziedzic@tieto.com \
--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