From: Ben Greear <greearb@candelatech.com>
To: Sebastian Gottschall <s.gottschall@dd-wrt.com>,
ath10k@lists.infradead.org
Subject: Re: possible memory leak or memory waste
Date: Mon, 25 May 2015 15:39:13 -0700 [thread overview]
Message-ID: <5563A491.8070701@candelatech.com> (raw)
In-Reply-To: <55639395.6070207@dd-wrt.com>
Default firmware has a hard-coded minimum number of tx buffers (somewhere
more than 1k buffers I think). Maybe driver is allocating all this
memory somehow?
If you do one-way traffic tests (udp), I wonder if you can tell if it is tx
or rx that consumes the memory?
CT firmware can be configured to use any multiple-of-8 amount of tx
buffers, though I have not tested below around 600.
Thanks,
Ben
On 05/25/2015 02:26 PM, Sebastian Gottschall wrote:
> today using the latest testing driver, i found out the memory consumption is unbelievable high.
> my router here has 64 mb ram. this ram is fully taken after some minutes by ath10k. but only if data flow present.
>
> here the results of "free" after some minutes
> root@DD-WRT:~# free
> total used free shared buffers
> Mem: 61636 58752 2884 0 2600
> -/+ buffers: 56152 5484
> Swap: 0 0 0
>
>
> now i terminate hostapd which controls the ath10k chipset
>
>
> root@DD-WRT:~# kill 902
> root@DD-WRT:~# free
> total used free shared buffers
> Mem: 61636 23212 38424 0 2416
> -/+ buffers: 20796 40840
> Swap: 0 0 0
>
>
> you see the difference?
>
>
> regards,
> Sebastian Gottschall
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2015-05-25 22:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 12:45 [PATCH] amth10k: fix promisc handling Michal Kazior
2015-05-21 5:40 ` Michal Kazior
2015-05-21 7:40 ` Kalle Valo
2015-05-25 12:25 ` Kalle Valo
2015-05-25 17:10 ` request: ACK timing setting required Sebastian Gottschall
2015-05-25 17:13 ` Ben Greear
2015-05-25 17:48 ` Sebastian Gottschall
2015-05-25 17:53 ` Ben Greear
2015-05-25 19:21 ` Sebastian Gottschall
2015-05-25 19:32 ` Ben Greear
2015-05-25 20:31 ` Sebastian Gottschall
2015-05-25 21:26 ` possible memory leak or memory waste Sebastian Gottschall
2015-05-25 22:39 ` Ben Greear [this message]
2015-05-25 23:00 ` Sebastian Gottschall
2015-05-25 23:42 ` Ben Greear
2015-05-26 0:07 ` Sebastian Gottschall
2015-05-26 5:42 ` Michal Kazior
2015-05-26 6:20 ` Rajkumar Manoharan
2015-05-26 7:26 ` Sebastian Gottschall
2015-05-26 7:23 ` Sebastian Gottschall
2015-05-26 8:26 ` Michal Kazior
2015-05-26 8:37 ` Sebastian Gottschall
2015-05-26 9:21 ` Michal Kazior
2015-05-26 11:19 ` Sebastian Gottschall
2015-05-27 10:25 ` [PATCH] amth10k: fix promisc handling Kalle Valo
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=5563A491.8070701@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=s.gottschall@dd-wrt.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