From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Tim Harvey <tharvey@gateworks.com>
Cc: Michal Kazior <michal.kazior@tieto.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: help troubleshooting low throughput
Date: Sun, 25 May 2014 10:32:52 +0300 [thread overview]
Message-ID: <87r43itisb.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAJ+vNU0KuGgGYVUyNbO=TTwH_P0zGszmFt6dBMWLNiO7APW0kw@mail.gmail.com> (Tim Harvey's message of "Fri, 23 May 2014 22:32:59 -0700")
Tim Harvey <tharvey@gateworks.com> writes:
>> Also, now that I think about you don't have a bridge. This means your
>> AP system has to perform a lot more packet mangling which I guess can
>> be pretty taxing for the A9.
>>
>
> yep - turns out it is a cpu bottleneck. I'm not sure what I was
> looking at when I checked the performance before but now I see that I
> am hitting 100% utilization.
>
> Putting the AP in a bridge and moving iperf off of it, brings up my
> TCP bandwidth to 240mbps (at which point the STA running iperf is 100%
> pegged) and 463mbps UDP (at which point the AP was 100% pegged).
Did you check that you had all kernel debug options disabled, including
ath10k debug options? Kernel debugging code can significantly decrease
maximum throughput.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2014-05-25 7:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 9:39 help troubleshooting low throughput Tim Harvey
2014-05-22 9:46 ` Tim Harvey
2014-05-22 10:08 ` Michal Kazior
2014-05-22 18:37 ` Tim Harvey
2014-05-23 7:42 ` Michal Kazior
2014-05-24 5:32 ` Tim Harvey
2014-05-25 7:32 ` Kalle Valo [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=87r43itisb.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=michal.kazior@tieto.com \
--cc=tharvey@gateworks.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