From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: General VHT rate-ctrl question
Date: Wed, 13 Apr 2016 10:01:24 +0200 [thread overview]
Message-ID: <1460534484.3057.2.camel@sipsolutions.net> (raw)
In-Reply-To: <570D8956.8090806@candelatech.com> (sfid-20160413_014843_049708_B2F53AD9)
On Tue, 2016-04-12 at 16:48 -0700, Ben Greear wrote:
> If a station and it's peer can both do VHT, is there ever a good
> reason to even try HT rates?
>
Not really; perhaps if you could do HT greenfield preamble (which VHT
doesn't have) you could get something out of it, beyond that I don't
see a reason to try.
Unless, for some strange reason, it supports only single stream VHT and
dual-stream HT or something really weird?
johannes
next prev parent reply other threads:[~2016-04-13 8:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 23:48 General VHT rate-ctrl question Ben Greear
2016-04-13 8:01 ` Johannes Berg [this message]
2016-04-13 13:18 ` Ben Greear
2016-04-13 17:01 ` Dave Taht
2016-04-13 20:07 ` Krishna Chaitanya
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=1460534484.3057.2.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.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;
as well as URLs for NNTP newsgroup(s).