From: Stanislaw Gruszka <sgruszka@redhat.com>
To: wwguy <wey-yi.w.guy@intel.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Intel Linux Wireless <ilw@linux.intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] iwlagn: use cts-to-self protection on 5000 adapters series
Date: Thu, 26 May 2011 13:17:53 +0200 [thread overview]
Message-ID: <20110526111752.GA20099@redhat.com> (raw)
In-Reply-To: <1306332806.17516.7.camel@wwguy-ubuntu>
On Wed, May 25, 2011 at 07:13:26AM -0700, wwguy wrote:
> On Wed, 2011-05-25 at 05:33 -0700, Stanislaw Gruszka wrote:
> > after some time, performance downgrade to unpached driver level, like
> unpatched?
> > However patch still make better here, since similar test on unpached
> unpatched?
I'll fix that.
> > + /*
> > + * force CTS-to-self frames protection if RTS-CTS is not preferred
> > + * one aggregation protection method
> on?
The sentence is not the best English, but replacing "one" to "on" will
not help, I think.
> if I remember correctly, the RTS/CTS was added to fix 6000 performance
> issue 2 years ago. Did you see the similar performance downgrade issue
> on other devices beside 5000?
No, I think only 5000 ware afected (also with random connection hangs).
Patching and using cts-to-self on 6000, give slightly better performance
here with 6300 adapter:
vanilla 6300 5Ghz: 8.13 8.03 8.13 8.03 8.19 avr 8.1020 std 0.070143
patched 6300 5Ghz: 8.60 8.59 8.60 8.41 8.57 avr 8.5540 std 0.081425
vanilla 6300 2GHz: 4.06 4.39 4.60 4.70 4.80 avr 4.5100 std 0.293770
patched 6300 2GHz: 4.94 4.90 4.94 5.05 4.88 avr 4.9420 std 0.065727
I plan to do more testing, but not yet (except 5000 adapters I have
quite good performance).
Stanislaw
next prev parent reply other threads:[~2011-05-26 11:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 12:33 [PATCH] iwlagn: use cts-to-self protection on 5000 adapters series Stanislaw Gruszka
2011-05-25 14:13 ` wwguy
2011-05-26 11:17 ` Stanislaw Gruszka [this message]
2011-05-26 14:21 ` wwguy
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=20110526111752.GA20099@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.