linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Cédric Debarge - ACKSYS" <cedric.debarge@acksys.fr>
To: "'Johannes Berg'" <johannes@sipsolutions.net>
Cc: <linux-wireless@vger.kernel.org>,
	"'Ben Greear'" <greearb@candelatech.com>
Subject: RE: [RFC 0/2] mac80211: add support for ht_caps mcs rxmask override
Date: Fri, 19 Feb 2016 17:39:14 +0100	[thread overview]
Message-ID: <01a201d16b34$11dcf5e0$3596e1a0$@acksys.fr> (raw)
In-Reply-To: <1455827262.2084.31.camel@sipsolutions.net>

> What are you working on that you need this?

We are working on critical industrial networks where a specific (generally high) bandwidth is required.
Supressing low MCSs (that are not able to handle the desired bandwidth) allows us to be sure that the wireless link can sustain the requested bandwidth.
If the radio conditions do not allow high enough MCSs, we prefer increase the AP density rather than not being able to communicate at the requested speed.
 
> I think my comments to him apply to this too - see the thread at
> http://thread.gmane.org/gmane.linux.kernel.wireless.general/143789

Thanks for the link, I didn't noticed Ben Grear's request.
According to the given patches, it seems the targeted goal is quite similar. So your comments also apply on my demand.

Anyway, thanks for your answer.

Cedric


  reply	other threads:[~2016-02-19 16:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-05 15:41 [RFC 0/2] mac80211: add support for ht_caps mcs rxmask override Cedric DEBARGE
2016-02-05 15:41 ` [RFC 1/2] cfg80211: " Cedric DEBARGE
2016-02-05 15:42 ` [RFC 2/2] nl80211: add nl attribute to set " Cedric DEBARGE
2016-02-18 20:27 ` [RFC 0/2] mac80211: add support for " Johannes Berg
2016-02-19 16:39   ` Cédric Debarge - ACKSYS [this message]
2016-02-23 11:08     ` 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='01a201d16b34$11dcf5e0$3596e1a0$@acksys.fr' \
    --to=cedric.debarge@acksys.fr \
    --cc=greearb@candelatech.com \
    --cc=johannes@sipsolutions.net \
    --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;
as well as URLs for NNTP newsgroup(s).