From: Kalle Valo <kvalo@qca.qualcomm.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [RFC/RFT 6/7] ath10k: add active htc ul pipe polling support
Date: Wed, 15 May 2013 15:37:35 +0300 [thread overview]
Message-ID: <87a9nwqv00.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1368185830-29519-7-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Fri, 10 May 2013 13:37:09 +0200")
Michal Kazior <michal.kazior@tieto.com> writes:
> Until now we depended solely on passive or lazy
> polling for tx completion.
>
> The passive was in htc rx handler. The lazy in
> htc_send_work(). The lazy would fire only if there
> are less than 50% resources free. However for HTT
> tx we have 2047 resources and we never used more
> than 512 (HTT_MAX_PENDING_TX).
>
> It is a good idea to have a timer that polls for
> tx completions "just in case". This could help if
> mac80211 is waiting for tx status and there's no
> tx/rx happening.
>
> Signed-off-by: Michal Kazior <michal.kazior@tieto.com>
I haven't tested your patches yet, but I'm a bit concerned about the
timer. Timers usually create problems of their own and using them wrong
affect power consumption.
I don't have time to read the patches in detail, but can you give a
short summary how the timer works? How often is it fired? What happens
when the data path is idle?
And is it absolutely necessary to use a timer? Can't we use tx
completions or some other existing event from firmware to accomplish the
same?
--
Kalle Valo
next prev parent reply other threads:[~2013-05-15 12:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 11:37 [ath9k-devel] [RFC/RFT 0/7] ath10k: tx flow control fixes Michal Kazior
2013-05-10 11:37 ` [ath9k-devel] [RFC/RFT 1/7] ath10k: change errno if we run out of msdu_ids Michal Kazior
2013-05-10 11:37 ` [ath9k-devel] [RFC/RFT 2/7] ath10k: ath10k_htc_prepare_tx_skb() never fails Michal Kazior
2013-05-10 11:37 ` [ath9k-devel] [RFC/RFT 3/7] ath10k: add lockdep asserts to htc skb dequeuing Michal Kazior
2013-05-10 11:37 ` [ath9k-devel] [RFC/RFT 4/7] ath10k: simplify htc flow control Michal Kazior
2013-05-10 11:37 ` [ath9k-devel] [RFC/RFT 5/7] ath10k: remove unused queue limit Michal Kazior
2013-05-10 11:37 ` [ath9k-devel] [RFC/RFT 6/7] ath10k: add active htc ul pipe polling support Michal Kazior
2013-05-15 12:37 ` Kalle Valo [this message]
2013-05-15 13:19 ` Michal Kazior
2013-05-10 11:37 ` [ath9k-devel] [RFC/RFT 7/7] ath10k: introduce proper htt tx flow control Michal Kazior
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=87a9nwqv00.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath9k-devel@lists.ath9k.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