linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: wwguy <wey-yi.w.guy@intel.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Intel Linux Wireless <ilw@linux.intel.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"stable@kernel.org" <stable@kernel.org>
Subject: Re: [PATCH v2] iwl3945: remove plcp check
Date: Wed, 09 Feb 2011 09:07:42 -0800	[thread overview]
Message-ID: <1297271262.20613.66.camel@wwguy-ubuntu> (raw)
In-Reply-To: <20110209074606.GA5528@redhat.com>

On Tue, 2011-02-08 at 23:46 -0800, Stanislaw Gruszka wrote:
> Patch fixes:
> https://bugzilla.redhat.com/show_bug.cgi?id=654599
>  
> Many users report very low speed problem on 3945 devices,
> this patch fixes problem, but only for some of them.
>  
> For unknown reason, sometimes after hw scanning, device is not able
> to receive frames at high rate. Since plcp health check may request
> hw scan to "reset radio", performance problem start to be observable
> after update kernel to .35, where plcp check was introduced.
> 
> Bug reporter confirmed that removing plcp check fixed problem for him.
>  
> Reported-and-tested-by: SilvioTO <silviotoya@yahoo.it>
> Cc: stable@kernel.org  # 2.6.35+
> Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
Acked-by: Wey-Yi Guy <wey-yi.w.guy@intel.com>
> ---
> v1 -> v2
> Instead of tuning threshold remove the check completely
> 
looks good for just minimal changes

Wey




      reply	other threads:[~2011-02-09 17:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-08  9:04 [PATCH] iwl3945: increase plcp check threshold Stanislaw Gruszka
2011-02-08 15:47 ` wwguy
2011-02-09  6:31   ` Stanislaw Gruszka
2011-02-09  7:46     ` [PATCH v2] iwl3945: remove plcp check Stanislaw Gruszka
2011-02-09 17:07       ` wwguy [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=1297271262.20613.66.camel@wwguy-ubuntu \
    --to=wey-yi.w.guy@intel.com \
    --cc=ilw@linux.intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sgruszka@redhat.com \
    --cc=stable@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).