All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Gottschall <s.gottschall@dd-wrt.com>
To: Ben Greear <greearb@candelatech.com>, ath10k@lists.infradead.org
Subject: Re: possible memory leak or memory waste
Date: Tue, 26 May 2015 02:07:16 +0200	[thread overview]
Message-ID: <5563B934.5050306@dd-wrt.com> (raw)
In-Reply-To: <5563B357.9060309@candelatech.com>

Am 26.05.2015 um 01:42 schrieb Ben Greear:
> Can you test with ath9k to make sure it is actually ath10k related?
already tested. this device has 2 chipsets. one is ath9k based and the 
second is ath10k based. :-)
only if i kill the hostapd process which controls ath10k. the memory 
waste is gone
>
> And/or try traffic in RX direction only to see if that still uses
> lots of memory?

>
> Does memory come back after you just stop traffic (w/out stopping
> hostapd)?
yes. slowly. its fluctuating. so sometimes there is 30 mb free again and 
seconds later just 2 mb. so very heavy changes. on bigger routers with 
more than 64 mb (i have a second here with 128 mb)
the total consumption stabilizes at 45 - 50 mb for the driver only which 
is still too much for sure.  so it may not a leak. but ath10k or the 
firmware is wasting too much memory for embedded devices
and ar9880 is just used on embedded devices almost
>
> Thanks,
> Ben
>
>
> On 05/25/2015 04:00 PM, Sebastian Gottschall wrote:
>> Am 26.05.2015 um 00:39 schrieb Ben Greear:
>>> 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?
>> its tx. i have a ethernet over ip tunnel running on that link and i 
>> broadcast iptv in that way. (its my way to convert multicast to unicast)
>> the  tunnel itself is rfc ethernet over ip, which is somewhat like 
>> udp. so connectionless protocol
>>
>> Sebastian
>>>
>>> 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
>>>>
>>>
>>
>


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

  reply	other threads:[~2015-05-26  0:07 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12 12:45 [PATCH] amth10k: fix promisc handling Michal Kazior
2015-05-12 12:45 ` Michal Kazior
2015-05-21  5:40 ` Michal Kazior
2015-05-21  5:40   ` Michal Kazior
2015-05-21  7:40   ` Kalle Valo
2015-05-21  7:40     ` Kalle Valo
2015-05-25 12:25     ` 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
2015-05-25 23:00                       ` Sebastian Gottschall
2015-05-25 23:42                         ` Ben Greear
2015-05-26  0:07                           ` Sebastian Gottschall [this message]
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
2015-05-27 10:25         ` 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=5563B934.5050306@dd-wrt.com \
    --to=s.gottschall@dd-wrt.com \
    --cc=ath10k@lists.infradead.org \
    --cc=greearb@candelatech.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.