All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xue Liu <xue.liu@dks-koeln.de>
To: Roman Yeryomin <leroi.lists@gmail.com>,
	"Manoharan, Rajkumar" <rmanohar@qti.qualcomm.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
	Rajkumar Manoharan <rmanohar@codeaurora.org>
Subject: Re: ath10k performance, master branch from 20160407
Date: Tue, 12 Apr 2016 12:16:29 +0200	[thread overview]
Message-ID: <20b024d0-9b33-39fd-c96a-189ed5bf2a4f@dks-koeln.de> (raw)
In-Reply-To: <CACiydbLHksfB68yOZq3SLuXEw-ucw5FnTDHq_un_Bpeah_5mZQ@mail.gmail.com>

Hello Roman,

I am also working on the 10k testing with armada 388 + QCA9880 and 
OpenWRT trunk (compat-wireless 20160110).


On 08/04/16 18:00, Roman Yeryomin wrote:
> Rajkumar,
>
> I took backports from
> git://git.kernel.org/pub/scm/linux/kernel/git/backports/backports.git,
> took latest ath tree from
> git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git, generated
> backports-output based on ath master branch, refreshed openwrt
> patches.
Can you share how to refreshed openwrt patches to include latest patches 
from ath10k. I have also get backports-output from ath10k kernel, but I 
don't know how to use them. Thank you.

Regards,

Xue Liu
> And saw big performance degradation. Am I doing something wrong?
>
> Regards,
> Roman
>
> On 8 April 2016 at 18:34, Manoharan, Rajkumar <rmanohar@qti.qualcomm.com> wrote:
>> Roman,
>>
>> Which backports version are you using? I don't see codel changes in ath.git/wireless-drivers.git.
>> Hope you are using same firmware.
>>
>> -Rajkumar
>> ________________________________________
>> From: ath10k <ath10k-bounces@lists.infradead.org> on behalf of Roman Yeryomin <leroi.lists@gmail.com>
>> Sent: Friday, April 8, 2016 8:14 PM
>> To: ath10k@lists.infradead.org
>> Subject: ath10k performance, master branch from 20160407
>>
>> Hello!
>>
>> I've seen performance patches were commited so I've decided to give it
>> a try (using 4.1 kernel and backports).
>> The results are quite disappointing: TCP download (client pov) dropped
>> from 750Mbps to ~550 and UDP shows completely weird behavour - if
>> generating 900Mbps it gives 30Mbps max, if generating 300Mbps it gives
>> 250Mbps, before (latest official backports release from January) I was
>> able to get 900Mbps.
>> Hardware is basically ap152 + qca988x 3x3.
>> When running perf top I see that fq_codel_drop eats a lot of cpu.
>> Here is the output when running iperf3 UDP test:
>>
>>      45.78%  [kernel]       [k] fq_codel_drop
>>       3.05%  [kernel]       [k] ag71xx_poll
>>       2.18%  [kernel]       [k] skb_release_data
>>       2.01%  [kernel]       [k] r4k_dma_cache_inv
>>       1.73%  [kernel]       [k] eth_type_trans
>>       1.24%  [kernel]       [k] build_skb
>>       1.20%  [mac80211]     [k] ieee80211_tx_dequeue
>>       1.03%  [kernel]       [k] __delay
>>       0.98%  [kernel]       [k] fq_codel_enqueue
>>       0.94%  [kernel]       [k] __netif_receive_skb_core
>>       0.93%  [kernel]       [k] skb_release_head_state
>>       0.88%  [ath10k_core]  [k] ath10k_htt_tx
>>       0.87%  [kernel]       [k] __dev_queue_xmit
>>       0.84%  [mac80211]     [k] ieee80211_tx_status
>>       0.81%  [kernel]       [k] __build_skb
>>       0.80%  [mac80211]     [k] __ieee80211_subif_start_xmit
>>       0.77%  [kernel]       [k] br_handle_frame_finish
>>       0.75%  [kernel]       [k] __qdisc_run
>>       0.73%  [kernel]       [k] skb_recycler_consume
>>       0.72%  [kernel]       [k] kfree_skb
>>       0.72%  [kernel]       [k] get_page_from_freelist
>>       0.69%  [kernel]       [k] br_fdb_update
>>       0.69%  [kernel]       [k] br_handle_frame
>>       0.67%  [kernel]       [k] __copy_user_common
>>       0.66%  [kernel]       [k] __skb_flow_dissect
>>       0.65%  [ath10k_core]  [k] ath10k_txrx_tx_unref
>>       0.60%  [kernel]       [k] kmem_cache_alloc
>>       0.60%  [mac80211]     [k] sta_addr_hash
>>       0.56%  [kernel]       [k] fq_codel_dequeue
>>       0.53%  [kernel]       [k] __local_bh_enable_ip
>>       0.50%  [kernel]       [k] __br_fdb_get
>>
>> What could be the reason?
>> I've seen there are some patches from Michal which touch fq_codel,
>> would those help or not?
>>
>>
>> Regards,
>> Roman
>>
>> _______________________________________________
>> ath10k mailing list
>> ath10k@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/ath10k
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
>


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

      parent reply	other threads:[~2016-04-12 10:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-08 14:44 Roman Yeryomin
2016-04-08 15:34 ` Manoharan, Rajkumar
2016-04-08 16:00   ` Roman Yeryomin
2016-04-08 16:41     ` Manoharan, Rajkumar
2016-04-08 17:19       ` Roman Yeryomin
2016-04-09  4:02         ` Manoharan, Rajkumar
2016-04-13 12:44           ` Roman Yeryomin
2016-04-17  9:28           ` Roman Yeryomin
2016-04-17 15:06             ` Manoharan, Rajkumar
2016-04-17 23:03               ` Roman Yeryomin
2016-04-18 13:00                 ` Roman Yeryomin
2016-04-19  5:28                   ` Michal Kazior
2016-04-19  7:31                     ` Roman Yeryomin
2016-04-19  7:43                       ` Michal Kazior
2016-04-19 15:35                         ` Valo, Kalle
2016-04-22 17:05                           ` Roman Yeryomin
2016-05-09 12:26                             ` Michal Kazior
2016-05-15 22:59                               ` Roman Yeryomin
2016-05-16  3:57                                 ` Rajkumar Manoharan
2016-04-22 17:03                         ` Roman Yeryomin
2016-04-22 17:02                     ` Roman Yeryomin
2016-04-20  9:03                 ` Michal Kazior
2016-04-12 10:16     ` Xue Liu [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=20b024d0-9b33-39fd-c96a-189ed5bf2a4f@dks-koeln.de \
    --to=xue.liu@dks-koeln.de \
    --cc=ath10k@lists.infradead.org \
    --cc=leroi.lists@gmail.com \
    --cc=rmanohar@codeaurora.org \
    --cc=rmanohar@qti.qualcomm.com \
    --subject='Re: ath10k performance, master branch from 20160407' \
    /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

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.