All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Ryazanov <ryazanov.s.a@gmail.com>
To: "Valo, Kalle" <kvalo@qca.qualcomm.com>
Cc: Adrian Chadd <adrian.chadd@gmail.com>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: QCA988X firmware pull-push support
Date: Wed, 1 Feb 2017 11:21:00 +0300	[thread overview]
Message-ID: <CAHNKnsSz_tz-7081SwpJ5+V7UMyOM1PXnHzf8cF1or4SVk9axQ@mail.gmail.com> (raw)
In-Reply-To: <87y3xtrmn2.fsf@kamboji.qca.qualcomm.com>

On Mon, Jan 30, 2017 at 11:13 AM, Valo, Kalle <kvalo@qca.qualcomm.com> wrote:
> Adrian Chadd <adrian.chadd@gmail.com> writes:
>
>> On 29 January 2017 at 17:20, Sergey Ryazanov <ryazanov.s.a@gmail.com> wrote:
>>> Yep. Looks like so.
>>
>> Which is good, because my FreeBSD ath10k port only works with 10.1 /
>> 10.2 firmware on earlier chips, and I haven't figured out the
>> intermediate software queue support that came with 10.4. :-)
>>
>> But yeah. I'll wake for Kalle to verify, but I think it's a 10.4
>> thing
>
> So there are two parts here, ieee80211_ops::wake_tx_queue() support in
> ath10k and ATH10K_FW_FEATURE_PEER_FLOW_CONTROL in firmware. We did have
> wake_tx_queue() support enabled for all hw/fw combinations but it was
> changed because some people claimed there are throughput regressions in
> certain cases. So for now we only enable wake_tx_queue() support only if
> firmware supports ATH10K_FW_FEATURE_PEER_FLOW_CONTROL:
>
>         if (!test_bit(ATH10K_FW_FEATURE_PEER_FLOW_CONTROL,
>                       ar->running_fw->fw_file.fw_features))
>                 ar->ops->wake_tx_queue = NULL;
>
> I remember that there were some improvements with wake_tx_queue() even
> if firmware didn't support ATH10K_FW_FEATURE_PEER_FLOW_CONTROL.

Yes, Rajkumar Manoharan made some fix for wake_tx_queue (). I think
that I could test this fix with QCA988x in the couple of weeks. May be
we could return to total intermediate queues support.

> I'm
> starting to wonder should we have a module parameter to force use of
> wake_tx_queue()?

Maybe. This could be useful at stage of final testing, if the last fix
for wake_tx_queue() really solves the performance issues. Before we
returning to total support of intermediate queues.

> And IIRC ATH10K_FW_FEATURE_PEER_FLOW_CONTROL was supported in some of
> 10.4 releases, but not all of them.

Yep, only few of 10.4 firmware have support of tx pull-push mode.

-- 
Sergey

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

      parent reply	other threads:[~2017-02-01  8:21 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-29 23:11 QCA988X firmware pull-push support Sergey Ryazanov
     [not found] ` <CAJ-Vmo=yD7Ct5LFXBO3qNhKsNco91VXMmZOYeBaAuw+DFGq=RQ@mail.gmail.com>
2017-01-30  1:20   ` Sergey Ryazanov
2017-01-30  2:50     ` Adrian Chadd
2017-01-30  8:13       ` Valo, Kalle
2017-01-30 10:28         ` 9984 VHT Sebastian Gottschall
2017-02-01 16:48           ` Ben Greear
2017-02-01 18:45             ` Sebastian Gottschall
2017-02-02 16:18               ` Ben Greear
2017-02-02 18:24                 ` Ben Greear
2017-02-02 18:42                   ` Sebastian Gottschall
2017-02-02 19:05                     ` Ben Greear
2017-02-02 19:08                       ` Sebastian Gottschall
2017-02-02 19:18                         ` Ben Greear
2017-02-02 19:29                           ` Sebastian Gottschall
2017-02-02 19:32                             ` Ben Greear
2017-02-02 20:28                               ` Sebastian Gottschall
2017-02-02 20:37                                 ` Ben Greear
2017-02-02 20:45                                   ` Sebastian Gottschall
2017-02-02 20:50                                     ` Ben Greear
2017-02-02 21:01                                       ` Sebastian Gottschall
2017-02-02 21:04                                       ` Sebastian Gottschall
2017-02-07 12:14                       ` Valo, Kalle
2017-02-07 12:39                         ` Sebastian Gottschall
2017-02-10  6:50                           ` Valo, Kalle
     [not found]                             ` <c894f9ae-068a-eac3-16e6-c1ada4da22b9@dd-wrt.com>
2017-02-14 10:30                               ` Valo, Kalle
2017-02-14 15:21                                 ` Sebastian Gottschall
2017-02-16 16:20                                   ` Adrian Chadd
2017-02-16 16:34                                     ` Sebastian Gottschall
2017-02-17  5:42                                       ` Adrian Chadd
2017-02-20 15:40                                   ` Valo, Kalle
2017-02-01  8:21         ` Sergey Ryazanov [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=CAHNKnsSz_tz-7081SwpJ5+V7UMyOM1PXnHzf8cF1or4SVk9axQ@mail.gmail.com \
    --to=ryazanov.s.a@gmail.com \
    --cc=adrian.chadd@gmail.com \
    --cc=ath10k@lists.infradead.org \
    --cc=kvalo@qca.qualcomm.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 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.