All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bjørn Mork" <bjorn@mork.no>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Emmanuel Grumbach <egrumbach@gmail.com>,
	linux-wireless@vger.kernel.org, ilw@linux.intel.com
Subject: Re: iwlmvm: High latencies and low RX rate with firmware version 22.24.8.0 but not with 22.1.7.0
Date: Thu, 24 Apr 2014 11:46:55 +0200	[thread overview]
Message-ID: <87oazrawkw.fsf@nemi.mork.no> (raw)
In-Reply-To: <1398326539.4154.0.camel@jlt4.sipsolutions.net> (Johannes Berg's message of "Thu, 24 Apr 2014 10:02:19 +0200")

Johannes Berg <johannes@sipsolutions.net> writes:

> On Thu, 2014-04-24 at 09:49 +0200, Bjørn Mork wrote:
>
>> I realize that icmp echos don't necessarily tell the whole truth, but
>> the same latency difference is noticable on e.g interactive ssh sessions
>> as well.  So I believe pinging illustrates the difference pretty well.
>> The *only* thing changed between these sessions is the iwl
>> firmware. Position, channel, driver, hardware is the same. This was
>> captured on 2.4GHz.
>
> There might be differences in how the driver treats the firmware - I
> think it probably turns off powersave for the older one. Have you tried
> turning it off manually?

Thanks for the tip.  Yes, it seems to be related to that.  Using

 modprobe iwlmvm power_scheme=1

avoids the problem. I also tried using

 modprobe iwlwifi power_save=N

with iwlmvm.power_scheme=2 (default), but that made no difference.  The
problem was still present with this setting.


Bjørn

      reply	other threads:[~2014-04-24  9:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24  7:49 iwlmvm: High latencies and low RX rate with firmware version 22.24.8.0 but not with 22.1.7.0 Bjørn Mork
2014-04-24  8:02 ` Johannes Berg
2014-04-24  9:46   ` Bjørn Mork [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=87oazrawkw.fsf@nemi.mork.no \
    --to=bjorn@mork.no \
    --cc=egrumbach@gmail.com \
    --cc=ilw@linux.intel.com \
    --cc=johannes@sipsolutions.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.