Linux wireless drivers development
 help / color / mirror / Atom feed
From: reinette chatre <reinette.chatre@intel.com>
To: Richard Farina <sidhayn@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: intel 5100/iwlagn bug in 2.6.35-rc2 during large file transfer
Date: Thu, 24 Jun 2010 10:48:51 -0700	[thread overview]
Message-ID: <1277401731.25793.2391.camel@rchatre-DESK> (raw)
In-Reply-To: <4C23961D.7050500@gmail.com>

On Thu, 2010-06-24 at 10:30 -0700, Richard Farina wrote:
> There were two compat-wireless releases for 2.6.35_rc2 because Luis had 
> asked me to test and then he changed it for the official release.  I'll 
> use the official 2.6.35_rc2 release for the current testing so if there 
> are any patches you wish to toss my way please base them on that.  The 
> other option is you tell me what to do, I can run any kernel, any git 
> snapshot, whatever you say.  Like I said, all I have to do is download 
> something or transfer something large so it is pretty easily 
> reproducible here so I'll test whatever you like.


Could you please try out this patch? It is based on the latest linux-2.6
so should apply cleanly to your latest 2.6.35 stable compat.

diff --git a/drivers/net/wireless/iwlwifi/iwl-agn-lib.c b/drivers/net/wireless/iwlwifi/iwl-agn-lib.c
index 0f292a2..028db74 100644
--- a/drivers/net/wireless/iwlwifi/iwl-agn-lib.c
+++ b/drivers/net/wireless/iwlwifi/iwl-agn-lib.c
@@ -613,7 +613,7 @@ void iwlagn_rx_allocate(struct iwl_priv *priv, gfp_t priority)
 		}
 		spin_unlock_irqrestore(&rxq->lock, flags);
 
-		if (rxq->free_count > RX_LOW_WATERMARK)
+		if (rxq->free_count > 8)
 			gfp_mask |= __GFP_NOWARN;
 
 		if (priv->hw_params.rx_page_order > 0)
diff --git a/drivers/net/wireless/iwlwifi/iwl-fh.h b/drivers/net/wireless/iwlwifi/iwl-fh.h
index 113c366..396a16c 100644
--- a/drivers/net/wireless/iwlwifi/iwl-fh.h
+++ b/drivers/net/wireless/iwlwifi/iwl-fh.h
@@ -426,7 +426,7 @@
  * RX related structures and functions
  */
 #define RX_FREE_BUFFERS 64
-#define RX_LOW_WATERMARK 8
+#define RX_LOW_WATERMARK 64
 
 /* Size of one Rx buffer in host DRAM */
 #define IWL_RX_BUF_SIZE_3K (3 * 1000) /* 3945 only */



  reply	other threads:[~2010-06-24 17:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-17  2:56 intel 5100/iwlagn bug in 2.6.35-rc2 during large file transfer Richard Farina
2010-06-17 23:35 ` Richard Farina
2010-06-22 16:48 ` reinette chatre
2010-06-24 16:12   ` Richard Farina
2010-06-24 17:13     ` reinette chatre
2010-06-24 17:30       ` Richard Farina
2010-06-24 17:48         ` reinette chatre [this message]
2010-06-25 16:28           ` Richard Farina
2010-06-25 18:57             ` reinette chatre
2010-06-27 17:14               ` Richard Farina
2010-06-28 16:27                 ` reinette chatre
2010-06-28 17:01                   ` Richard Farina
2010-06-28 20:39                     ` reinette chatre
2010-06-29  3:57                       ` Richard Farina
2010-06-30 23:32                         ` reinette chatre

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=1277401731.25793.2391.camel@rchatre-DESK \
    --to=reinette.chatre@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sidhayn@gmail.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