linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Igor Plyatov <plyatov@gmail.com>
To: Daniel Halperin <dhalperi@cs.washington.edu>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
	Ivo Van Doorn <ivdoorn@gmail.com>,
	linux-usb@vger.kernel.org, linux-wireless@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.38: rt2800usb: high latency (1000ms)?
Date: Thu, 14 Apr 2011 09:38:56 +0400	[thread overview]
Message-ID: <4DA68870.7090109@gmail.com> (raw)
In-Reply-To: <BANLkTin5VwUryoMK=jYpbNTudPLufZ+RDw@mail.gmail.com>

Dear Daniel,
> On Wed, Apr 13, 2011 at 1:13 PM, Justin Piszcz<jpiszcz@lucidpixels.com>  wrote:
>>> (1) What is the AP's beacon period and DTIM? Typical values are 100
>>> TUs for beacons (102.4 ms) and 2 for DTIM (2 beacons per power-save
>>> wakeup) which should imply a mean of 100 and max of 200 ms delay even
>>> on pings.
>> I am using a WNDR3700 with default settings in terms of beacons/etc.  No
>> issues with any device (laptop, computer, etc (in windows)), I have two
>> wireless USB adapters (bought two) and in Windows, no problems, I don't
>> think
>> it is the WNDR3700.  As far as linux/wpa-supplicant, using default settings.
> Not enough info. What does "iw dev wlan1 scan dump"  (it might not be
> wlan1 for you) say for "beacon interval"?
>
> Does anyone know how to get the DTIM period out of iw?
>
# iw dev wlan0 scan dump
BSS 74:ea:3a:e4:fa:6e (on wlan0) -- associated
     TSF: 499843461 usec (0d, 00:08:19)
     freq: 2442
     beacon interval: 100
     capability: ESS Privacy ShortPreamble ShortSlotTime (0x0431)
     signal: -51.00 dBm
     last seen: 510 ms ago
     Information elements from Probe Response frame:
     SSID: mynet2
     Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0
     DS Parameter set: channel 7
     RSN:     * Version: 1
          * Group cipher: CCMP
          * Pairwise ciphers: CCMP
          * Authentication suites: PSK
          * Capabilities: (0x0000)
     ERP: <no flags>
     Extended supported rates: 24.0 36.0 48.0 54.0
     WMM:     * Parameter version 1
          * u-APSD
          * BE: CW 15-1023, AIFSN 3
          * BK: CW 15-1023, AIFSN 7
          * VI: CW 7-15, AIFSN 2, TXOP 3008 usec
          * VO: acm CW 3-7, AIFSN 2, TXOP 1504 usec
     HT capabilities:
         Capabilities: 0x104e
             HT20/HT40
             SM Power Save disabled
             RX HT40 SGI
             No RX STBC
             Max AMSDU length: 3839 bytes
             DSSS/CCK HT40
         Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
         Minimum RX AMPDU time spacing: 8 usec (0x06)
         HT RX MCS rate indexes supported: 0-15
         HT TX MCS rate indexes are undefined
     WPS:     * Version: 1.0
          * Wi-Fi Protected Setup State: 2 (Configured)
          * Response Type: 3 (AP)
          * Unknown TLV (0x1047, 16 bytes): 00 00 00 00 00 00 10 00 00 
00 74 ea 3a e4 fa 6e
          * Manufacturer: TP-LINK
          * Model: TL-WR1043N
          * Model Number: 1.0
          * Serial Number: 1.0
          * Primary Device Type: 6-0050f204-1
          * Device name: Wireless Router TL-WR1043N
          * Config methods: Ethernet, Label, PBC
          * RF Bands: 0x1

>>> (2) How long does the client wait after waking up to go back to sleep?
>>> It should be at least a few seconds. For ssh, then, you should see
>>> something like a 100-200 ms delay for the first key and then nothing
>>> at all unless you stop typing for a bit.
>> It lags with each word I type, it is terrible.  If I run something like
>> dmesg or ps auxww, the entire session freezes for 5-10 seconds before it
>> comes back.
> Sorry; I meant what is the software stack configured to do? Do some
> looking around.
What do you mean here?

Best regards!
--
Igor Plyatov

  parent reply	other threads:[~2011-04-14  5:39 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13 15:47 2.6.38: rt2800usb: high latency (1000ms)? Justin Piszcz
2011-04-13 15:59 ` Ivo Van Doorn
2011-04-13 16:01   ` Justin Piszcz
     [not found]     ` <BANLkTinxkXi6WnAyXoZLDR+uyL+TmevuPw@mail.gmail.com>
2011-04-13 16:25       ` Daniel Halperin
2011-04-13 17:57         ` Justin Piszcz
2011-04-13 18:37           ` Daniel Halperin
2011-04-13 20:13             ` Justin Piszcz
2011-04-13 20:31               ` Daniel Halperin
2011-04-13 20:36                 ` Justin Piszcz
2011-04-13 22:26                   ` Joshua Scoggins
2011-04-14  5:38                 ` Igor Plyatov [this message]
2011-04-14  5:17               ` Igor Plyatov
2011-04-13 16:11   ` Walter Goldens
2011-04-13 18:44   ` Marc Dietrich
2011-04-25 18:35 ` 2.6.38: rt2800usb: driver is crashing the kernel Justin Piszcz
2011-04-25 20:52   ` Roland Dreier
2011-04-25 20:56     ` Justin Piszcz
2011-04-26 10:22     ` Justin Piszcz
2011-04-26 21:53       ` Justin Piszcz
2011-04-26 22:30         ` Larry Finger
2011-04-26 23:31           ` Justin Piszcz
2011-04-27  0:29             ` Jano
2011-05-02 23:46             ` Justin Piszcz
2011-05-03  1:15               ` Larry Finger
2011-05-03 12:53                 ` Walter Goldens
2011-05-03 13:08                   ` Jools Wills
2011-05-26 16:24                     ` Justin Piszcz

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=4DA68870.7090109@gmail.com \
    --to=plyatov@gmail.com \
    --cc=dhalperi@cs.washington.edu \
    --cc=ivdoorn@gmail.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux-wireless@vger.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).