linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org,
	Vincent Fann <vincent_fann@realtek.com>,
	Shao Fu <shaofu@realtek.com>, Stable <stable@vger.kernel.org>
Subject: Re: [PATCH 4.1] rtlwifi: Remove the clear interrupt routine from all drivers
Date: Wed, 20 May 2015 16:53:51 +0300	[thread overview]
Message-ID: <877fs39wy8.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1431743367-10059-1-git-send-email-Larry.Finger@lwfinger.net> (Larry Finger's message of "Fri, 15 May 2015 21:29:27 -0500")

Larry Finger <Larry.Finger@lwfinger.net> writes:

> From: Vincent Fann <vincent_fann@realtek.com>
>
> Several of these drivers have there TX randomly blocked for 3~5 seconds while
> measuring tx throughput (iperf). The root couse happens in rtl_pci_flush().
> The function uses a while-loop to wait for TX queue length to decrease to 0.
> The TX queue length counts the number of packets that are queued in the driver.
> The driver relys on the TX OK interrupt to return skb and reduce TX queue length.
>
> The interrupt subroutine disables interupts, reads the interrupt registers, and
> then clears the registers in the beginning of _rtl_pci_interrupt(). After all
> interupts process are finished, the driver invokes enable_interrupt() to enable
> interupts. This behavior is normal for an interrupt subroutine.
>
> But enable_interrupt() invokes clear_interrupt() again. This unexpected interrupt
> clearing may cleari me fresh TX OK interrupts. These missing interrupts cause TX
> queue length to never reduce to 0i, which causes rtl_pci_flush() to be stuck in
> unterminated while-loop.
>
> This patch removes clear_interrupt() in enable_interrupt() to avoid this behavior.
>
> Signed-off-by: Vincent Fann <vincent_fann@realtek.com>
> Signed-off-by: Shao Fu <shaofu@realtek.com>
> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
> Cc: Stable <stable@vger.kernel.org> [3.18+]
> ---
>
> Kalle,
>
> This patch is a little large for the current kernel and stable; however, it only
> deletes code that is clearly wrong. I hope it will be OK.

This isn't a recent regression nor a crasher (or similar) so I can't
really justify to send this to 4.1 this late. The way I see it this
could easily wait for 4.2, right?

-- 
Kalle Valo

  reply	other threads:[~2015-05-20 13:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-16  2:29 [PATCH 4.1] rtlwifi: Remove the clear interrupt routine from all drivers Larry Finger
2015-05-20 13:53 ` Kalle Valo [this message]
2015-05-20 15:34   ` Larry Finger
2015-05-26 10:59 ` [4.1] " Kalle Valo

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=877fs39wy8.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=shaofu@realtek.com \
    --cc=stable@vger.kernel.org \
    --cc=vincent_fann@realtek.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).