All of lore.kernel.org
 help / color / mirror / Atom feed
From: "voncken" <cedric.voncken@acksys.fr>
To: "'Adrian Chadd'" <adrian@freebsd.org>,
	"'Felix Fietkau'" <nbd@openwrt.org>
Cc: "'Mohammed Shafi'" <shafi.wireless@gmail.com>,
	<linux-wireless@vger.kernel.org>
Subject: RE: [RFC] ATH9K: infinite loop in Tasklet
Date: Wed, 2 Jan 2013 14:17:40 +0100	[thread overview]
Message-ID: <016301cde8eb$8b92ba60$a2b82f20$@acksys.fr> (raw)
In-Reply-To: <CAJ-Vmo=kbvLSdA8wGaRacAOvoZBdksJwQZ+Z52RbiUAq-T4weA@mail.gmail.com>

	Thanks for your answer. 

	I found a workaround for my problem. 

	In my Linux kernel, the default SLAB allocator was changed in
default settings. 
	SLOB  was used in place of SLAB. 
	I select the SLAB allocator and that fix the default because it runs
faster. 

	However  the infinite loop can still happen if the cpu is heavily
loaded with other tasklets. 

	Best regards.

Cedric Voncken 
-----Message d'origine-----
De : adrian.chadd@gmail.com [mailto:adrian.chadd@gmail.com] De la part de
Adrian Chadd
Envoyé : mercredi 2 janvier 2013 00:41
À : Felix Fietkau
Cc : Mohammed Shafi; Cedric VONCKEN; linux-wireless@vger.kernel.org
Objet : Re: [RFC] ATH9K: infinite loop in Tasklet

On 1 January 2013 07:18, Felix Fietkau <nbd@openwrt.org> wrote:

> I think the best way to properly fix this issue is to implement NAPI 
> support (which mac80211 already supports).

Sure, but there may be some underlying issues (maybe even on just that
particular platform) that need to be addressed.

Migrating to NAPI / breaking out of the tasklet early should also be done,
but it's potentially orthogonal to the OP's problem.


Adrian


  reply	other threads:[~2013-01-02 13:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-11 10:01 [RFC] ATH9K: infinite loop in Tasklet Cedric VONCKEN
2012-12-30 14:19 ` Mohammed Shafi
2013-01-01  4:20   ` Adrian Chadd
2013-01-01 15:18     ` Felix Fietkau
2013-01-01 23:40       ` Adrian Chadd
2013-01-02 13:17         ` voncken [this message]
2013-01-02 16:21           ` Adrian Chadd
2013-01-02 17:15             ` voncken
2013-01-02 20:13               ` Adrian Chadd
2013-01-02 20:48                 ` Felix Fietkau
2013-01-02 23:12                   ` Adrian Chadd
2013-01-02 23:22                     ` Felix Fietkau
2013-01-03  1:36                       ` Adrian Chadd
  -- strict thread matches above, loose matches on Subject: below --
2012-12-07 15:27 Cedric VONCKEN
2012-12-07 13:52 Cedric VONCKEN

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='016301cde8eb$8b92ba60$a2b82f20$@acksys.fr' \
    --to=cedric.voncken@acksys.fr \
    --cc=adrian@freebsd.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbd@openwrt.org \
    --cc=shafi.wireless@gmail.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.