From: Felix Fietkau <nbd@openwrt.org>
To: Tim Harvey <tharvey@gateworks.com>, linux-wireless@vger.kernel.org
Cc: linville@tuxdriver.com
Subject: Re: [PATCH 2/2] ath9k: add a recv budget
Date: Tue, 22 Apr 2014 11:09:11 +0200 [thread overview]
Message-ID: <535631B7.7050208@openwrt.org> (raw)
In-Reply-To: <1398122097-23544-2-git-send-email-tharvey@gateworks.com>
On 2014-04-22 01:14, Tim Harvey wrote:
> Implement a recv budget so that in cases of high traffic we still allow other
> taskets to get processed.
>
> Without this, we can encounter a host of issues during high wireless traffic
> reception depending on system load including rcu stall's detected (ARM),
> soft lockups, failure to service critical tasks such as watchdog resets,
> and triggering of the tx stuck tasklet.
>
> The same thing was proposed previously by Ben:
> http://www.spinics.net/lists/linux-wireless/msg112891.html
>
> The only difference here is that I make sure only processed packets are counted
> in the budget by checking at the end of the rx loop.
>
> Signed-off-by: Tim Harvey <tharvey@gateworks.com>
For both patches:
Acked-by: Felix Fietkau <nbd@openwrt.org>
next prev parent reply other threads:[~2014-04-22 9:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 23:14 [PATCH 1/2] ath9k: fix possible hang on flush Tim Harvey
2014-04-21 23:14 ` [PATCH 2/2] ath9k: add a recv budget Tim Harvey
2014-04-22 9:09 ` Felix Fietkau [this message]
2014-04-29 12:04 ` [ath9k-devel] " Tim Harvey
2014-04-29 12:04 ` Tim Harvey
2014-04-29 12:25 ` [ath9k-devel] " Felix Fietkau
2014-04-29 12:25 ` Felix Fietkau
2014-04-29 19:23 ` Adrian Chadd
2014-04-29 12:02 ` [ath9k-devel] [PATCH 1/2] ath9k: fix possible hang on flush Tim Harvey
2014-04-29 12:02 ` Tim Harvey
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=535631B7.7050208@openwrt.org \
--to=nbd@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=tharvey@gateworks.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.