ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Rajkumar Manoharan <rmanohar@qti.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH v2 0/7] ath10k: add copy engine fast path support
Date: Fri, 16 Oct 2015 15:51:44 +0300	[thread overview]
Message-ID: <87pp0fgen3.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1444654626-3290-1-git-send-email-rmanohar@qti.qualcomm.com> (Rajkumar Manoharan's message of "Mon, 12 Oct 2015 18:26:59 +0530")

Rajkumar Manoharan <rmanohar@qti.qualcomm.com> writes:

> Below patchset adds fast path support for uplink traffic by bypassing
> HTC layer processing. This is enabled by making use of unused copy
> engine 5 to receive HTT messages directly from HIF layer. From initial
> validation in VHT80/5G mode TCP UL is improved to 900Mbps from ~840Mbps
> in conducted test.
>
> -Rajkumar
>
> v2:
>  * fix invalid dma memory access (ATH10K_SKB_RXCB is used instead of
>    ATH10K_SKB_CB in htt_tx_cb)
>  * register either send_cb or recv_cb callback not both for
>    appropriate CE.
>  * Process CE 4 send completion first before processing rx
>  
> Rajkumar Manoharan (7):
>   ath10k: export htc tx rx handlers
>   ath10k: register per copy engine send completion callbacks
>   ath10k: register per copy engine receive callbacks
>   ath10k: export htt tx rx handlers
>   ath10k: Configure copy engine 5 for HTT messages
>   ath10k: remove unused dl_is_polled
>   ath10k: remove htc polling for tx completion

All 7 applied, thanks. I wasn't able to reproduce the warning anymore,
tested with both qca988x and qca99x0.

-- 
Kalle Valo

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

  parent reply	other threads:[~2015-10-16 12:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12 12:56 [PATCH v2 0/7] ath10k: add copy engine fast path support Rajkumar Manoharan
2015-10-12 12:57 ` [PATCH v2 1/7] ath10k: export htc tx rx handlers Rajkumar Manoharan
2015-10-12 12:57 ` [PATCH v2 2/7] ath10k: register per copy engine send completion callbacks Rajkumar Manoharan
2015-10-12 12:57 ` [PATCH v2 3/7] ath10k: register per copy engine receive callbacks Rajkumar Manoharan
2015-10-12 12:57 ` [PATCH v2 4/7] ath10k: export htt tx rx handlers Rajkumar Manoharan
2015-10-12 12:57 ` [PATCH v2 5/7] ath10k: Configure copy engine 5 for HTT messages Rajkumar Manoharan
2015-10-12 12:57 ` [PATCH v2 6/7] ath10k: remove unused dl_is_polled Rajkumar Manoharan
2015-10-12 12:57 ` [PATCH v2 7/7] ath10k: remove htc polling for tx completion Rajkumar Manoharan
2015-10-16 12:51 ` Kalle Valo [this message]
     [not found] ` <CACiydbLcjNGdpc+dtBFCTAUrC0RtEhtxoxf3+XhXk24soX_qQg@mail.gmail.com>
2016-01-31  6:31   ` [PATCH v2 0/7] ath10k: add copy engine fast path support Manoharan, Rajkumar
2016-01-31 12:41     ` Roman Yeryomin
2016-01-31 14:23       ` Manoharan, Rajkumar
2016-01-31 17:20         ` Roman Yeryomin
2016-02-01  9:54         ` Roman Yeryomin
2016-02-01 12:35           ` Roman Yeryomin
2016-02-04 17:53             ` Roman Yeryomin

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=87pp0fgen3.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rmanohar@qti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox