linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Rob Browning <rlb@defaultvalue.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Slow receive with rtl8192cu (usb ew-7811Un)
Date: Mon, 29 Aug 2011 19:58:57 -0500	[thread overview]
Message-ID: <4E5C35D1.80600@lwfinger.net> (raw)
In-Reply-To: <874o41rqrg.fsf@trouble.defaultvalue.org>

[-- Attachment #1: Type: text/plain, Size: 1092 bytes --]

On 06/07/2011 09:38 PM, Rob Browning wrote:
> Rob Browning<rlb@defaultvalue.org>  writes:
>
>> As another data point, I just tested the same device on a second machine
>> (a desktop), and saw the same behavior -- initially high transfer rates
>> trailing off to about 60K/s.
>
> ...and another data point.  Just to be sure it wasn't that particular
> usb device, I got another that I think is the same hardware (this time
> the Airlink 101), and I see exactly the same behavior.
>
> Next I'll try a different access point -- I'll let you know what I find.
> And if there's anything else I can do to help test, please let me know.

It has been some time since you wrote this. Any changes?

I recently noticed a slow-down on my rtl8192cu doing TX TCP MAERTS tests with 
netperf. The attached patch seemed to help. If you still have the problem, does 
it help? Note: The patch is badly named - I started trying to fix a problem 
connecting with a 270 Mpbs 2.4 GHz channel. It works with 150 Mbps. On the 
higher speed network, it authenticates and associates, but no data gets through.

Larry



[-- Attachment #2: rtlwifi_fix_wpa --]
[-- Type: text/plain, Size: 818 bytes --]

Index: wireless-testing-new/drivers/net/wireless/rtlwifi/core.c
===================================================================
--- wireless-testing-new.orig/drivers/net/wireless/rtlwifi/core.c
+++ wireless-testing-new/drivers/net/wireless/rtlwifi/core.c
@@ -610,6 +610,11 @@ static void rtl_op_bss_info_changed(stru
 
 			mac->link_state = MAC80211_NOLINK;
 			memset(mac->bssid, 0, 6);
+
+			/* reset sec info */
+			rtl_cam_reset_sec_info(hw);
+
+			rtl_cam_reset_all_entry(hw);
 			mac->vendor = PEER_UNKNOWN;
 
 			RT_TRACE(rtlpriv, COMP_MAC80211, DBG_DMESG,
@@ -1063,6 +1068,9 @@ static int rtl_op_set_key(struct ieee802
 		 *or clear all entry here.
 		 */
 		rtl_cam_delete_one_entry(hw, mac_addr, key_idx);
+
+		rtl_cam_reset_sec_info(hw);
+
 		break;
 	default:
 		RT_TRACE(rtlpriv, COMP_ERR, DBG_EMERG,

      parent reply	other threads:[~2011-08-30  0:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-14 17:01 Slow receive with rtl8192cu (usb ew-7811Un) Rob Browning
2011-05-16  0:50 ` Larry Finger
2011-05-16  2:26   ` Rob Browning
2011-05-16  3:39     ` Larry Finger
2011-05-16  5:18       ` Rob Browning
2011-05-16 15:12         ` Larry Finger
2011-05-17  3:41           ` Rob Browning
2011-05-17  3:57             ` Rob Browning
2011-05-17 16:34               ` Larry Finger
2011-05-17 23:04                 ` Rob Browning
2011-05-24  6:18                   ` Rob Browning
2011-06-04 20:32               ` Rob Browning
2011-06-08  2:38                 ` Rob Browning
2011-06-12 18:06                   ` Rob Browning
2011-07-10 20:24                     ` Rob Browning
2011-08-30  0:58                   ` Larry Finger [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=4E5C35D1.80600@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rlb@defaultvalue.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).