From: Ben Greear <greearb@candelatech.com>
To: Gaurang Ramesh Naik <gaurang@vt.edu>, ath10k@lists.infradead.org
Subject: Re: Dynamic Bandwidth in hw rate control
Date: Wed, 08 Jun 2016 22:23:55 -0700 [thread overview]
Message-ID: <5758FD6B.40409@candelatech.com> (raw)
In-Reply-To: <CAFc9h7uxTOUxONvW-gvgkFLUNR9OBn09kfetF9gqAtcNqN3SLg@mail.gmail.com>
On 06/08/2016 08:10 PM, Gaurang Ramesh Naik wrote:
> Hi,
>
> I needed a small clarification related to dynamic bandwidth setup. The
> documentation in wmi.h says " When enabled HW rate control tries
> different bandwidths when retransmitting frames."
>
> Does this mean that each packet is first always tried over VHT80 and
> if that fails it goes to HT40 and then to HT20? I tried this with one
> AP-Sta operating in VHT80 and one AP operating in its first secondary
> channel. When I check the rx rate info using "iw dev wlanx station
> dump", the bandwidth seems to sometimes alternate between 20 and 80,
> but sometimes it stays fixed at 20. Hence, I was wondering what really
> happens.
For one thing, if the hardware detects interference on secondary channels,
then it may decide to transmit a 20Mhz encoding.
The rate-ctrl algs in the firmware differ from release to release, but
the general goal is to transmit with the fastest encoding rate.
Thanks,
Ben
>
> Thanks,
> Gaurang.
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-06-09 5:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 3:10 Dynamic Bandwidth in hw rate control Gaurang Ramesh Naik
2016-06-09 5:23 ` Ben Greear [this message]
2016-06-16 19:57 ` Gaurang Ramesh Naik
2016-06-16 20:06 ` Dave Taht
2016-06-16 20:54 ` Ben Greear
2016-06-16 22:44 ` Gaurang Ramesh Naik
2016-06-17 0:11 ` Ben Greear
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=5758FD6B.40409@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=gaurang@vt.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.