From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Wey-Yi Guy <wey-yi.w.guy@intel.com>,
Intel Linux Wireless <ilw@linux.intel.com>,
linux-wireless@vger.kernel.org
Subject: Re: [RFC/RFT] iwl3945: use software scanning by default
Date: Mon, 14 Feb 2011 13:40:23 +0100 [thread overview]
Message-ID: <20110214124022.GA14827@redhat.com> (raw)
In-Reply-To: <1297685299.3785.32.camel@jlt3.sipsolutions.net>
On Mon, Feb 14, 2011 at 01:08:19PM +0100, Johannes Berg wrote:
> On Tue, 2011-02-08 at 14:36 +0100, Stanislaw Gruszka wrote:
> > Looking for some more testing and opinions.
> >
> > Patch fixes:
> > https://bugzilla.redhat.com/show_bug.cgi?id=671366
> > and probably some other "very poor performance" bugs reported
> > elsewhere.
> >
> > Sometimes after hardware scanning device is unable to receive frames
> > at higher rate, what cause that very slow speed is observed by the users.
>
> Is there any more information about this problem?
Only valuable data we have is on above bugzilla report:
- messages with IWL_DEBUG_SCAN and some other flags:
https://bugzilla.redhat.com/attachment.cgi?id=476229
- wireshark capture:
https://bugzilla.redhat.com/attachment.cgi?id=476614
There is lots of ubuntu users discussion here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/621265?comments=all
Most important information there is that removing plcp check
and/or not using NetworkManager helps (both triggers scans).
Stanislaw
prev parent reply other threads:[~2011-02-14 12:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 13:36 [RFC/RFT] iwl3945: use software scanning by default Stanislaw Gruszka
2011-02-08 15:50 ` wwguy
2011-02-09 6:45 ` Stanislaw Gruszka
2011-02-14 12:08 ` Johannes Berg
2011-02-14 12:40 ` Stanislaw Gruszka [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=20110214124022.GA14827@redhat.com \
--to=sgruszka@redhat.com \
--cc=ilw@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=wey-yi.w.guy@intel.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 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.