archive mirror
 help / color / mirror / Atom feed
From: "Muna Sinada" <>
To: "'Johannes Berg'" <>
Cc: <>
Subject: RE: [PATCH v2] nl80211: Add HE UL MU fixed rate setting
Date: Thu, 26 Aug 2021 16:08:34 -0700	[thread overview]
Message-ID: <001601d79acf$4bb85b80$e3291280$> (raw)
In-Reply-To: <>

Hello Johannes,

I agree that it is odd to combine this new attribute with the existing parameters. I will be removing "he_ul_mcs" out of cfg80211_bitrate_mask and passing it as a separate attribute in next version.

Thank you,

-----Original Message-----
From: Johannes Berg <> 
Sent: Tuesday, August 17, 2021 6:49 AM
To: Muna Sinada <>
Subject: Re: [PATCH v2] nl80211: Add HE UL MU fixed rate setting


On Thu, 2021-07-29 at 12:41 -0700, Muna Sinada wrote:
> This patch adds nl80211 definitions, policies and parsing code 
> required to pass HE UL MU fixed rate settings.

I don't understand how this is sufficient?

>  		enum nl80211_txrate_gi gi;
>  		enum nl80211_he_gi he_gi;
>  		enum nl80211_he_ltf he_ltf;

Previously, for HE rates, we had configurations for:
 * HE guard interval

I guess I can sort of follow that uplink traffic is a bit different and not already configured by the setting for rate control we have today, but why does it not need all these parameters?

Also, why is this not a per-station parameter? OK, maybe we don't really want it to be a per-station parameter, or maybe the firmware/algorithm that's selecting things there can't deal with that, but it feels odd to combine it with the "rate control fixed rate" parameters you have here, and do that without even any explanation of how this is supposed to work.

This is going to need some work.


  reply	other threads:[~2021-08-26 23:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-29 19:41 Muna Sinada
2021-08-17 13:48 ` Johannes Berg
2021-08-26 23:08   ` Muna Sinada [this message]
2021-09-14  5:57     ` Kalle Valo

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='001601d79acf$4bb85b80$e3291280$' \ \ \ \
    --subject='RE: [PATCH v2] nl80211: Add HE UL MU fixed rate setting' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).