From: Bob Copeland <me@bobcopeland.com>
To: Fabio Rossi <rossi.f@inwind.it>
Cc: linux-wireless@vger.kernel.org,
Arnd Hannemann <hannemann@nets.rwth-aachen.de>,
ath5k-devel@lists.ath5k.org
Subject: Re: ath5k: 2.6.32-rc6 "no further txbuf available, dropping packet"
Date: Fri, 8 Jan 2010 22:41:32 -0500 [thread overview]
Message-ID: <20100109034132.GA18279@hash.localnet> (raw)
In-Reply-To: <201001082334.16066.rossi.f@inwind.it>
On Fri, Jan 08, 2010 at 11:34:16PM +0100, Fabio Rossi wrote:
> Hi Bob,
> I have tried your patch as I get many errors as in subject when I transfer
> huge files (I'm using as a test a 1GB file). With the patch I have the same
> errors.
>
> I'm using wireless-testing.git (v2.6.33-rc2-47131-gc72a18c) in managed mode
> (no AP).
Ok, well the patch only will affect AP mode -- it addresses a bug where
multicast AP frames are queued but not always processed. I wonder if your
workload is just filling up the queues and then the queues are awakened
prematurely. There's a check in ath5k_tx_processq to only re-enable the
queue when there are 40 tx buffers left, but there are a few other paths
that re-enable the queues -- also accounting on txbuf_len could theoretically
get broken.
Maybe a printk in ath5k_tx_queue of sc->txbuf_len caN show how many buffers
are typically available when entering?
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2010-01-09 3:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 17:12 ath5k: 2.6.32-rc6 "no further txbuf available, dropping packet" Arnd Hannemann
2009-11-11 4:13 ` Bob Copeland
2009-12-14 15:30 ` ath5k: 2.6.32-rc6 David Srbecky
2010-01-08 22:34 ` ath5k: 2.6.32-rc6 "no further txbuf available, dropping packet" Fabio Rossi
2010-01-09 3:41 ` Bob Copeland [this message]
2010-01-12 0:19 ` Fabio Rossi
2010-01-12 16:35 ` Bob Copeland
2010-01-13 21:28 ` Fabio Rossi
2010-01-20 10:39 ` ath5k: 2.6.32-rc6 "no further txbuf available, dropping packet" Pavel Ulpi
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=20100109034132.GA18279@hash.localnet \
--to=me@bobcopeland.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=hannemann@nets.rwth-aachen.de \
--cc=linux-wireless@vger.kernel.org \
--cc=rossi.f@inwind.it \
/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.