From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: OOM with pktgen when transmitting on ath10k station in 4.7.10+ kernel
Date: Mon, 28 Nov 2016 15:54:55 -0800 [thread overview]
Message-ID: <583CC3CF.1040101@candelatech.com> (raw)
When I over-drive ath10k station using pktgen, system goes OOM quickly. If I catch it in time
and stop pktgen, then memory is recovered over the next few seconds. I assume that there is an
un-bounded queue somewhere.
But, I cannot find any queues in the mac80211 tx path that apply to ath10k (as far as I can tell).
The one possibility is the pending queues, but printing them out with debugfs shows them all
zeros, and I have some code to bound them at 1000 pkts anyway.
I didn't see anything obvious in ath10k either, but I must be missing something...
pktgen transmits under the queue logic, so it will likely be ignoring any
queue-stopped signals from mac80211.
Are there any other places that pkts can be queued()?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
reply other threads:[~2016-11-28 23:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=583CC3CF.1040101@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).