From: Larry Finger <Larry.Finger@lwfinger.net>
To: Chr <chunkeey@web.de>
Cc: Johannes Berg <johannes@sipsolutions.net>,
davem@davemloft.net, John W Linville <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] p54: Fix regression due to commit b19fa1f
Date: Wed, 06 Aug 2008 22:33:51 -0500 [thread overview]
Message-ID: <489A6D1F.1040409@lwfinger.net> (raw)
In-Reply-To: <200808070057.01952.chunkeey@web.de>
Chr wrote:
> On Monday 04 August 2008 23:14:51 Larry Finger wrote:
>> In commit b19fa1fa91845234961c64dbd564671aa7c0fd27, the configuration
>> parameter NETDEVICES_MULTIQUEUE was eliminated making multiple TX queues
>> the normal behavior. For p54usb, enabling multiple queues broke the driver.
>>
>> The real failure is not known, but a temporary hack that forces only one
>> queue is presented here.
>>
>
> The real problem seems to be that skb_get_queue_mapping doesn't
> work the way it should when we process the firmwares callback. It's
> always "0" and unfortunately also when it should be something else like
> queue 1, 2 or 3..... problem solved?
>
> However someone should really take a closer look at the multiqueue thing,
> especially why it has to BLOCK/SPIN (uninterruptible?) when a queue is stopped
> and tx returns therefore NETDEV_BUSY.
> The is assumption that "a queue is in any case going to become free again" is
> well-intentioned, but as my devices are crashing left & right on a daily basis
> it's even dangerous for my RAID ;-).
>
> (BTW: patch is diffed against 2.6.27-rc2)
>
> Signed-off-by: Christian Lamparter <chunkeey@web.de>
>
These changes fix the problem on my system. If it is made into a proper patch,
I'll ACK it.
Larry
next prev parent reply other threads:[~2008-08-07 3:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 21:14 [PATCH] p54: Fix regression due to commit b19fa1f Larry Finger
2008-08-06 22:57 ` Chr
2008-08-07 3:33 ` Larry Finger [this message]
2008-08-07 7:33 ` Chr
2008-08-07 6:35 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2008-08-07 13:21 Larry Finger
2008-08-07 13:27 ` Johannes Berg
2008-08-07 15:20 ` Larry Finger
2008-08-07 15:27 ` Chr
2008-08-07 15:26 ` Johannes Berg
2008-08-07 15:27 ` Johannes Berg
2008-08-07 16:00 ` Chr
2008-08-07 16:34 ` Michael Buesch
2008-08-07 15:59 ` Larry Finger
2008-08-07 23:18 ` Chr
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=489A6D1F.1040409@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=chunkeey@web.de \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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