From: Fabio Rossi <rossi.f@inwind.it>
To: linux-wireless@vger.kernel.org
Cc: Bob Copeland <me@bobcopeland.com>,
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: Wed, 13 Jan 2010 22:28:47 +0100 [thread overview]
Message-ID: <201001132228.47730.rossi.f@inwind.it> (raw)
In-Reply-To: <b6c5339f1001120835p381b440fgc2b30369737e104c@mail.gmail.com>
On Tuesday 12 January 2010 17:35:04 Bob Copeland wrote:
> Ok, well then at least we know that it is working :) Do you get any ill
> effects besides the log spam? If so then there could be an issue with
> starvation of the processing tasklet. Or maybe we should look at changing
> the limits for better flow.
I don't have problems with the connection but sometimes it's seems less
responsive, for instance it seems the latency in loading the web pages is
longer. Of course this is a personal impression.
I'm available to test any patches if you think the behavior may be improved,
also simply to investigate more on the issue.
Fabio
next prev parent reply other threads:[~2010-01-13 21:45 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
2010-01-12 0:19 ` Fabio Rossi
2010-01-12 16:35 ` Bob Copeland
2010-01-13 21:28 ` Fabio Rossi [this message]
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=201001132228.47730.rossi.f@inwind.it \
--to=rossi.f@inwind.it \
--cc=ath5k-devel@lists.ath5k.org \
--cc=hannemann@nets.rwth-aachen.de \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.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 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).