From: Quintin Pitts <geek4linux@gmail.com>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com, sean@mess.org
Subject: Re: [RFT/RFC] p54pci: prevent stuck rx-ring on slow system
Date: Sun, 04 Apr 2010 05:20:38 -0500 [thread overview]
Message-ID: <4BB867F6.3050208@gmail.com> (raw)
In-Reply-To: <201004032309.13029.chunkeey@googlemail.com>
On Sat Apr 03 2010 16:09:12 GMT-0500 (CDT), Christian Lamparter wrote:
> From: Quintin Pitts <geek4linux@gmail.com>
>
> This patch fixes an old problem, which - under certain
> circumstances - could cause the device to become
> unresponsive.
>
> most of p54pci's rx-ring management is implemented in just
> two distinct standalone functions. p54p_check_rx_ring takes
> care of processing incoming data, while p54p_refill_rx_ring
> tries to replenish all depleted communication buffers.
>
> This has always worked fine on my fast machine, but
> now I know there is a hidden race...
>
> The most likely candidate here is ring_control->device_idx.
> Quintin Pitts had already analyzed the culprit and posted
> a patch back in Oct 2009. But sadly, no one's picked up on this.
> ( https://patchwork.kernel.org/patch/53079/ [2 & 3] ).
> This patch goes in the same way, except that we now prioritize
> rx data processing, simply because tx routine can wait.
>
> Reported-by: Sean Young <sean@mess.org>
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=11386
> Reported-by: Quintin Pitts <geek4linux@gmail.com>
> Signed-off-by: Quintin Pitts <geek4linux@gmail.com>
> Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
> ---
> Quintin, I've added the "From: ...", because this is from your post.
> So, you've the last word, if you don't agree with what just I wrote.
>
I agree with what you wrote.
Thanks.
Quintin.
prev parent reply other threads:[~2010-04-04 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-03 21:09 [RFT/RFC] p54pci: prevent stuck rx-ring on slow system Christian Lamparter
2010-04-04 10:20 ` Quintin Pitts [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=4BB867F6.3050208@gmail.com \
--to=geek4linux@gmail.com \
--cc=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sean@mess.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).