From: "Manoharan, Rajkumar" <rmanohar@qti.qualcomm.com>
To: Roman Yeryomin <leroi.lists@gmail.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCH v2 0/7] ath10k: add copy engine fast path support
Date: Sun, 31 Jan 2016 14:23:12 +0000 [thread overview]
Message-ID: <1454250192327.17956@qti.qualcomm.com> (raw)
In-Reply-To: <CACiydbLk5=EH8Nz=FnL+B3itfXiRLbLUARg4ovWe7okLsZzyRQ@mail.gmail.com>
>On 31 January 2016 at 08:31, Manoharan, Rajkumar
><rmanohar@qti.qualcomm.com> wrote:
>>>> 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.
>>>>
>>>
>>>Hi Rajkumar,
>>>
>>>I'm very curious what hardware did you use to do the tests?
>>>Because with Dragonfly+Peregrine 3x3 I'm able to get only ~550Mbps :(
>>>
>>
>> Roman,
>>
>> It is verified in AP148 platform which IPQ8064 (1.4GHz dual core) platform.
>> Throughput will be lower in low end systems like AP135 (unicore processor).
>
> OK, but QSDK built with proprietary driver can reach 800Mbps at least.
> 900/800 Mbps difference is fine (ethernet software bridging is >900,
> e.g.) but 900/550 Mbps difference is not fine, there must be something
> ath10k is not doing or doing in a wrong way.
While ago, Michal did an experiments to improve performance by offloading
encap/decap to firmware. Can you try with below patch set? I hope there might
be some conflicts since the change is outdated. Please make sure to enable
CONFIG_ATH10K_802_3_FORMAT switch.
http://lists.infradead.org/pipermail/ath10k/2014-December/003935.html
In one of my experiments, replacing netif_receive_skb to netif_rx in mac80211/rx.c
had improved rx performance in AP135. I dont have data right now. Can you give a try?
-Rajkumar
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-01-31 14:23 UTC|newest]
Thread overview: 25+ 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:56 ` Rajkumar Manoharan
2015-10-12 12:57 ` [PATCH v2 1/7] ath10k: export htc tx rx handlers Rajkumar Manoharan
2015-10-12 12:57 ` 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 ` 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 ` Rajkumar Manoharan
2015-10-12 12:57 ` [PATCH v2 4/7] ath10k: export htt tx rx handlers Rajkumar Manoharan
2015-10-12 12:57 ` 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 ` Rajkumar Manoharan
2015-10-12 12:57 ` [PATCH v2 6/7] ath10k: remove unused dl_is_polled Rajkumar Manoharan
2015-10-12 12:57 ` Rajkumar Manoharan
2015-10-12 12:57 ` [PATCH v2 7/7] ath10k: remove htc polling for tx completion Rajkumar Manoharan
2015-10-12 12:57 ` Rajkumar Manoharan
2015-10-16 12:51 ` [PATCH v2 0/7] ath10k: add copy engine fast path support Kalle Valo
2015-10-16 12:51 ` Kalle Valo
[not found] ` <CACiydbLcjNGdpc+dtBFCTAUrC0RtEhtxoxf3+XhXk24soX_qQg@mail.gmail.com>
2016-01-31 6:31 ` Manoharan, Rajkumar
2016-01-31 12:41 ` Roman Yeryomin
2016-01-31 14:23 ` Manoharan, Rajkumar [this message]
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=1454250192327.17956@qti.qualcomm.com \
--to=rmanohar@qti.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=leroi.lists@gmail.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.