From: Michael Buesch <mb@bu3sch.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC/RFT 0/4] mac80211 QoS-related enhancements
Date: Wed, 30 Apr 2008 22:59:47 +0200 [thread overview]
Message-ID: <200804302259.47950.mb@bu3sch.de> (raw)
In-Reply-To: <1209560849.18659.1.camel@johannes.berg>
On Wednesday 30 April 2008 15:07:29 Johannes Berg wrote:
>
> > Any testing of this series is welcome, even just the first patch by itself
> > (especially with drivers other than b43), it doesn't make sense to test with
> > patch 2 and not 3 though, so if you're going to test one by one treat 2/3 as
> > a set.
>
> I have, of course, tested this series with b43 (and founds dozens of
> bugs...) Michael, thanks for your dma overflow injection feature :)
:)
> One thing that turned up was that if I enable dma overflow with this
> patchset then b43 hardware spews lots of PHY TX errors. I have verified
> that the ieee80211_tx_control info is correct, and the frame data is
> also fine, so I'm not sure what's up there. Could that be unrelated to
> this patch? I haven't tested dma overflow injection w/o this series yet.
Hm, not sure. It could be a b43 bug, of course. But last time I tested
the overflow injection, it worked fine. And that's not too long ago.
Probably 3 or 4 weeks. Of course, we should test this again with the QOS
patch applied and removed now. If that patch does actually trigger it,
then we probably still need to search for a b43 bug.
Is the QOS callback (forgot its name) called when we have an overflow?
--
Greetings Michael.
prev parent reply other threads:[~2008-04-30 21:00 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 12:40 [RFC/RFT 0/4] mac80211 QoS-related enhancements Johannes Berg
2008-04-30 12:40 ` [RFC/RFT 1/4] mac80211: use rate index in TX control Johannes Berg
2008-04-30 12:40 ` [RFC/RFT 2/4] GSO: generalize for mac80211 Johannes Berg
2008-05-06 16:12 ` Johannes Berg
2008-04-30 12:40 ` [RFC/RFT 3/4] mac80211: use GSO for fragmentation Johannes Berg
2008-05-07 7:10 ` Herbert Xu
2008-05-07 8:50 ` Johannes Berg
2008-05-07 9:00 ` Herbert Xu
2008-05-07 11:22 ` [PATCH] mac80211: rewrite fragmentation code Johannes Berg
2008-05-07 11:41 ` Herbert Xu
2008-05-07 11:52 ` Johannes Berg
2008-05-07 13:05 ` Herbert Xu
2008-05-07 13:48 ` Michael Buesch
2008-05-08 3:22 ` Herbert Xu
2008-05-08 3:26 ` David Miller
2008-05-08 9:00 ` Johannes Berg
2008-05-16 2:01 ` Rusty Russell
2008-05-16 3:28 ` Herbert Xu
2008-05-16 4:58 ` David Miller
2008-05-16 10:32 ` Rusty Russell
2008-05-16 10:38 ` Johannes Berg
2008-05-16 12:15 ` Herbert Xu
2008-05-16 19:40 ` David Miller
2008-05-19 3:08 ` Rusty Russell
2008-05-19 7:03 ` David Miller
2008-05-08 13:00 ` Michael Buesch
2008-05-08 13:08 ` Herbert Xu
2008-05-08 13:13 ` Michael Buesch
2008-05-08 13:15 ` Michael Buesch
2008-05-08 13:32 ` Herbert Xu
2008-05-07 19:19 ` Johannes Berg
2008-04-30 12:40 ` [RFC/RFT 4/4] mac80211: use multi-queue master netdevice Johannes Berg
2008-04-30 14:37 ` Ivo van Doorn
2008-04-30 14:45 ` Johannes Berg
2008-04-30 15:00 ` Johannes Berg
2008-04-30 15:34 ` Ivo van Doorn
2008-04-30 15:38 ` Johannes Berg
2008-05-01 8:21 ` Ivo van Doorn
2008-05-01 8:54 ` Johannes Berg
2008-04-30 19:39 ` Waskiewicz Jr, Peter P
2008-04-30 20:07 ` Johannes Berg
2008-04-30 13:07 ` [RFC/RFT 0/4] mac80211 QoS-related enhancements Johannes Berg
2008-04-30 20:59 ` Michael Buesch [this message]
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=200804302259.47950.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=johannes@sipsolutions.net \
--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).