mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Daniel Halperin <dhalperi@cs.washington.edu>
Cc: 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: Wed, 13 Apr 2011 16:13:02 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1104131605010.10727@p34.internal.lan> (raw)
In-Reply-To: <BANLkTinLRVyKwBA7ZbEXKqa18V=+a6+cZg@mail.gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 3316 bytes --]



On Wed, 13 Apr 2011, Daniel Halperin wrote:

> On Wed, Apr 13, 2011 at 10:57 AM, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
>> Hi,
>>
>> When powersave is enabled, it is very jumpy, I've used satellite comms
>> before
>> and (~600ms-1200ms was more smooth) as it did not jump around as much.  The
>> application is just a standalone desktop with minimal activity for the
>> majority
>> of the time, maybe thats why..
>>
>> With powersave disabled, I now see 0% packet loss (802.11n) and low ping
>> times, this looks like the proper solution for the wireless USB device I
>> am using.  By the way, is it possible/are there wireless USB devices out
>> there
>> that support wake on wireless lan (WOWL?
>>
>> Your ping command with power off:
>> 1408 bytes from server (192.168.1.2): icmp_req=539 ttl=64 time=1.07 ms
>> 1408 bytes from server (192.168.1.2): icmp_req=540 ttl=64 time=1.31 ms
>> 1408 bytes from server (192.168.1.2): icmp_req=541 ttl=64 time=1.07 ms
>> 1408 bytes from server (192.168.1.2): icmp_req=542 ttl=64 time=1.26 ms
>>
>> Your ping command with power on:
>> 1408 bytes from server (192.168.1.2): icmp_req=649 ttl=64 time=1.80 ms
>> 1408 bytes from server (192.168.1.2): icmp_req=650 ttl=64 time=1.85 ms
>> 1408 bytes from server (192.168.1.2): icmp_req=651 ttl=64 time=2.86 ms
>> 1408 bytes from server (192.168.1.2): icmp_req=652 ttl=64 time=1.46 ms
>>
>> You are correct, if there is a lot of traffic, its good, but if the system
>> is relatively idle and all that's going on is an SSH session, there is
>> horrible
>> latency.
>
> Gotcha. I might still look around in the network stack and/or driver
> and see what the time constants are. For instance:
>
> (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.


>
> (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.


>
> I'm SSHing over a Wi-Fi link that uses power save right this second,
> and have for years. It's not generally an issue, I suspect something
> worse is going on.
Maybe the wireless usb adapters do not function well in Linux with power save
on.

I bought them awhile ago, they had the highest reviews, and in Windows,
they did do 10-15MiB/s, in Linux, I see ~4.6MiB/s (but that was with power 
save on) about the same, 4.5MiB/s.
http://www.amazon.com/Medialink-Wireless-Adapter-802-11n-Compatible/dp/B002RM08RE

100+0 records in
100+0 records out
104857600 bytes (105 MB) copied, 23.2803 s, 4.5 MB/s

Justin.

  reply	other threads:[~2011-04-13 20:13 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13 15:47 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 [this message]
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
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=alpine.DEB.2.02.1104131605010.10727@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=dhalperi@cs.washington.edu \
    --cc=ivdoorn@gmail.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

all inboxes | Powered by JetHome®