From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Marek Kwaczynski <marek.kwaczynski@tieto.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH V2] ath10k: add recalc RTS/CTS protection method
Date: Thu, 13 Mar 2014 07:16:46 +0200 [thread overview]
Message-ID: <87txb2d6f5.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1393837661-15235-1-git-send-email-marek.kwaczynski@tieto.com> (Marek Kwaczynski's message of "Mon, 3 Mar 2014 10:07:41 +0100")
Marek Kwaczynski <marek.kwaczynski@tieto.com> writes:
> Add recalculation of RTS/CTS protection when one or more legacy
> stations are connected to ath10k. In this case enable RTS/CTS
> protection and set sw retry profile are needed in the FW.
> Without this change legacy station is starved and has very low
> throughput.
>
> Signed-off-by: Marek Kwaczynski <marek.kwaczynski@tieto.com>
Thanks, applied.
--
Kalle Valo
prev parent reply other threads:[~2014-03-13 5:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 9:07 [PATCH V2] ath10k: add recalc RTS/CTS protection method Marek Kwaczynski
2014-03-13 5:16 ` Kalle Valo [this message]
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=87txb2d6f5.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marek.kwaczynski@tieto.com \
/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).