From: "Alessandro Suardi" <alessandro.suardi@gmail.com>
To: "Zhu Yi" <yi.zhu@intel.com>
Cc: "Andrew Morton" <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
"James Ketrenos" <jketreno@linux.intel.com>,
netdev@vger.kernel.org
Subject: Re: [2.6.16-gitX] heavy performance regression in ipw2200 wireless driver
Date: Sat, 25 Mar 2006 23:48:29 +0100 [thread overview]
Message-ID: <5a4c581d0603251448k1df0c7bdob1f7a2a39749a8be@mail.gmail.com> (raw)
In-Reply-To: <1143171674.17270.195.camel@debian.sh.intel.com>
On 3/24/06, Zhu Yi <yi.zhu@intel.com> wrote:
> On Thu, 2006-03-23 at 15:02 +0100, Alessandro Suardi wrote:
> > That scp test shows 50%ish - but that was a quickie. The VNC
> > client even reported a 719Kbps throughput down from the more
> > usual 11500Kbps it starts off with. The first scp I tried when the
> > sluggishness was intolerable was going at 200KB/s - which
> > shows the problem can easily get in the neighborhood of an
> > order of magnitude.
>
> What kind of wireless encryption do you use? We turned off hardware
> encryption by default recently as a workaround for a firmware restart
> bug. You might want to load module with "modprobe ipw2200 hwcrypto=1"
> and retest.
The issue seems to have vanished in more recent kernel snapshots
(namely, 2.6.16-git3 and -git5 exhibited the problem; -git8 and -git9
did not).
I will holler if the problem pops up again... thanks,
--alessandro
"Dreamer ? Each one of us is a dreamer. We just push it down deep because
we are repeatedly told that we are not allowed to dream in real life"
(Reinhold Ziegler)
prev parent reply other threads:[~2006-03-25 22:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5a4c581d0603221724m391f5466l8a2af3ae7f0aacae@mail.gmail.com>
2006-03-23 3:10 ` [2.6.16-gitX] heavy performance regression in ipw2200 wireless driver Andrew Morton
2006-03-23 14:02 ` Alessandro Suardi
2006-03-24 3:41 ` Zhu Yi
2006-03-24 9:30 ` Alessandro Suardi
2006-03-25 22:48 ` Alessandro Suardi [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=5a4c581d0603251448k1df0c7bdob1f7a2a39749a8be@mail.gmail.com \
--to=alessandro.suardi@gmail.com \
--cc=akpm@osdl.org \
--cc=jketreno@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yi.zhu@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 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).