From: Arnd Hannemann <hannemann@nets.rwth-aachen.de>
To: ath5k-devel@lists.ath5k.org,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: ath5k: 2.6.32-rc6 "no further txbuf available, dropping packet"
Date: Tue, 10 Nov 2009 18:12:25 +0100 [thread overview]
Message-ID: <4AF99EF9.4040408@nets.rwth-aachen.de> (raw)
Hi,
is there any reason the packet is dropped and "NETDEV_TX_OK" is returned,
in this case?
Seems pretty stupid to me, because now we are randomly dropping
packets before kernel queuing (qdisc etc) can handle them,
or am I missing something?
Best regards,
Arnd
next reply other threads:[~2009-11-10 17:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 17:12 Arnd Hannemann [this message]
2009-11-11 4:13 ` ath5k: 2.6.32-rc6 "no further txbuf available, dropping packet" 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
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=4AF99EF9.4040408@nets.rwth-aachen.de \
--to=hannemann@nets.rwth-aachen.de \
--cc=ath5k-devel@lists.ath5k.org \
--cc=linux-wireless@vger.kernel.org \
/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).