All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Ben Greear <greearb@candelatech.com>
Cc: ath10k@lists.infradead.org
Subject: Re: Anyone done long term testing?
Date: Fri, 24 Jan 2014 21:18:34 +0200	[thread overview]
Message-ID: <874n4t2np1.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <52E2BB17.1010309@candelatech.com> (Ben Greear's message of "Fri,  24 Jan 2014 11:12:23 -0800")

Ben Greear <greearb@candelatech.com> writes:

> On 01/24/2014 11:03 AM, Kalle Valo wrote:
>> Ben Greear <greearb@candelatech.com> writes:
>> 
>>> I left an ath10k system up overnight, running 128kbps traffic on each
>>> of 32 stations, and by morning, the machine was OOM.
>> 
>> Did you see SWBA overrun warnings before the OOM? I saw one report of
>> such issue. This patch should help with that:
>> 
>> 748afc4 ath10k: implement and use new beacon method
>> 
>>> Just curious if anyone had done overnight traffic runs with any luck?
>> 
>> I'm running our AP135 board with ath9k+ath10k as my main AP and have
>> seen SWBA overruns few times, otherwise it has been pretty stable. But I
>> haven't yet tested with the patch above to see if the SWBA overruns are
>> really gone.
>
> I didn't notice any SWBA warnings, but perhaps they were there.
> I'll keep a look out for them if it happens again.
>
> I'm also running in station mode, with lots of station vifs, so might be
> hitting some issue specific to that.  I guess in station mode I shouldn't
> be sending any beacons anyway, so probably not the beacon issue.

Heh, I didn't realise that you were using station mode. Then most likely
you are seeing something else.

-- 
Kalle Valo

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

      reply	other threads:[~2014-01-24 19:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-24 16:54 Anyone done long term testing? Ben Greear
2014-01-24 17:10 ` Dave Taht
2014-01-24 19:03 ` Kalle Valo
2014-01-24 19:12   ` Ben Greear
2014-01-24 19:18     ` 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=874n4t2np1.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.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.