From: Sebastian Gottschall <s.gottschall@dd-wrt.com>
To: Rajkumar Manoharan <rmanohar@qti.qualcomm.com>,
Michal Kazior <michal.kazior@tieto.com>
Cc: Ben Greear <greearb@candelatech.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: possible memory leak or memory waste
Date: Tue, 26 May 2015 09:26:08 +0200 [thread overview]
Message-ID: <55642010.2070902@dd-wrt.com> (raw)
In-Reply-To: <20150526062009.GA14525@qca.qualcomm.com>
good point. ath10k is configured with one additional vap for me. but not
multi client.
both vap's are running in ap mode. let me send you my hostapd config here.
passphrases has been masked
driver=nl80211
ctrl_interface=/var/run/hostapd
wmm_ac_bk_cwmin=4
wmm_ac_bk_cwmax=10
wmm_ac_bk_aifs=7
wmm_ac_bk_txop_limit=0
wmm_ac_bk_acm=0
wmm_ac_be_aifs=3
wmm_ac_be_cwmin=4
wmm_ac_be_cwmax=10
wmm_ac_be_acm=0
wmm_ac_vi_aifs=2
wmm_ac_vi_cwmin=3
wmm_ac_vi_cwmax=4
wmm_ac_vi_txop_limit=94
wmm_ac_vi_acm=0
wmm_ac_vo_aifs=2
wmm_ac_vo_cwmin=2
wmm_ac_vo_cwmax=3
wmm_ac_vo_txop_limit=47
wmm_ac_vo_acm=0
tx_queue_data3_aifs=7
tx_queue_data3_cwmin=15
tx_queue_data3_cwmax=1023
tx_queue_data3_burst=0
tx_queue_data2_aifs=3
tx_queue_data2_cwmin=15
tx_queue_data2_cwmax=63
tx_queue_data1_aifs=1
tx_queue_data1_cwmin=7
tx_queue_data1_cwmax=15
tx_queue_data1_burst=3.0
tx_queue_data0_aifs=1
tx_queue_data0_cwmin=3
tx_queue_data0_cwmax=7
tx_queue_data0_burst=1.5
country_code=DE
tx_queue_data2_burst=2.0
wmm_ac_be_txop_limit=64
ieee80211n=1
dynamic_ht40=0
ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][DSSS_CCK-40]
vht_capab=[RXLDPC][SHORT-GI-80][TX-STBC-2BY1][RX-STBC1][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][MAX-MPDU-11454][MAX-A-MPDU-LEN-EXP7]
ieee80211ac=1
vht_oper_chwidth=1
vht_oper_centr_freq_seg0_idx=106
hw_mode=a
channel=100
frequency=5500
beacon_int=100
dtim_period=2
interface=ath1
disassoc_low_ack=1
wds_sta=1
wmm_enabled=1
bssid=E8:CC:18:FF:E0:A4
ignore_broadcast_ssid=0
max_num_sta=256
ssid=dd-wrt-NA-5
bridge=br0
logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2
dump_file=/tmp/hostapd.dump
eapol_version=1
eapol_key_index_workaround=0
wpa=2
wpa_passphrase=***********
wpa_key_mgmt=WPA-PSK
wpa_pairwise=CCMP
wpa_group_rekey=3600
bss=ath1.1
disassoc_low_ack=1
wmm_enabled=1
bssid=EA:CC:18:FF:E0:A4
ignore_broadcast_ssid=0
max_num_sta=256
ssid=dd-wrt-TV
bridge=br0
logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2
dump_file=/tmp/hostapd.dump
eapol_version=1
eapol_key_index_workaround=0
wpa=2
wpa_passphrase=************
wpa_key_mgmt=WPA-PSK
wpa_pairwise=CCMP
wpa_group_rekey=3600
Am 26.05.2015 um 08:20 schrieb Rajkumar Manoharan:
> On Tue, May 26, 2015 at 07:42:35AM +0200, Michal Kazior wrote:
>> On 26 May 2015 at 02:07, Sebastian Gottschall <s.gottschall@dd-wrt.com> wrote:
>>> 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
>> Keep in mind that hostapd itself requires memory to function as well.
>> Each process (and thread) need some internal kernel memory (stack, et
>> al).
>>
> Have seen simialar issue long hours run in mbssid mode with multi-client.
> Killing hostapd regains memory.
>
> [<c021dd44>] (unwind_backtrace) from [<c021ae0c>] (show_stack+0x10/0x14)
> [<c021ae0c>] (show_stack) from [<c0336b9c>] (dump_stack+0x88/0xcc)
> [<c0336b9c>] (dump_stack) from [<c0279804>] (dump_header.isra.11+0x64/0x178)
> [<c0279804>] (dump_header.isra.11) from [<c0279b10>] (oom_kill_process+0x70/0x384)
> [<c0279b10>] (oom_kill_process) from [<c027a2a0>] (out_of_memory+0x2d4/0x304)
> [<c027a2a0>] (out_of_memory) from [<c027d180>] (__alloc_pages_nodemask+0x608/0x664)
> [<c027d180>] (__alloc_pages_nodemask) from [<c0278780>] (filemap_fault+0x1f8/0x390)
> [<c0278780>] (filemap_fault) from [<c028f45c>] (__do_fault+0xa4/0x42c)
> [<c028f45c>] (__do_fault) from [<c0292494>] (handle_mm_fault+0x230/0x7b0)
> [<c0292494>] (handle_mm_fault) from [<c021f70c>] (do_page_fault+0x114/0x26c)
> [<c021f70c>] (do_page_fault) from [<c0208440>] (do_PrefetchAbort+0x34/0x98)
>
> Need to check whether it is a regression or not.
>
> -Rajkumar
>
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2015-05-26 7:26 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
2015-05-26 5:42 ` Michal Kazior
2015-05-26 6:20 ` Rajkumar Manoharan
2015-05-26 7:26 ` Sebastian Gottschall [this message]
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=55642010.2070902@dd-wrt.com \
--to=s.gottschall@dd-wrt.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
--cc=michal.kazior@tieto.com \
--cc=rmanohar@qti.qualcomm.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.