From: "Klaus Müller" <kmueller@justmail.de>
To: "Richard Schütz" <r.schtz@t-online.de>, linux-wireless@vger.kernel.org
Subject: Re: broken ath9k-driver - problems with creating new TCP-connections. Bad performance
Date: Sun, 27 Mar 2011 17:39:35 +0200 [thread overview]
Message-ID: <4D8F5A37.9070306@justmail.de> (raw)
In-Reply-To: <4D8F50A6.70508@t-online.de>
Richard Schütz wrote:
>> If the AP is set to HT20, this driver doesn't use IEEE 802.11n any more,
>> or, to say it more specific: the selected bit rate is max. 64 Mb/s and
>> the performance is even worse.
>
> Of course it uses 802.11n, but only with 20 MHz channel width, so the
> data rate is lower than with 40 Mhz channel width. The highest rate of
> 802.11g is 54 Mbit/s anyway.
I know - but there isn't any difference between g and n with 20 MHz
channel in real performance. That's why I wrote the driver wouldn't use
n any more. But this wasn't correct with respect of the technical view.
>> I'm wondering at all, why the ath9k driver doesn't switch to 300 Mb/s:
>> the rt3572sta-driver doesn't have any problem with both settings.
>
> Your AR9285 only supports up to 150 Mbit/s.
Now it's clear, why 150 Mbit/s is the maximum.
Klaus
next prev parent reply other threads:[~2011-03-27 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-27 12:08 broken ath9k-driver - problems with creating new TCP-connections. Bad performance Klaus Müller
2011-03-27 12:36 ` Felix Fietkau
2011-03-27 14:37 ` Klaus Müller
2011-03-27 14:57 ` Felix Fietkau
2011-03-27 15:08 ` Richard Schütz
[not found] ` <4D8F50A6.70508@t-online.de>
2011-03-27 15:39 ` Klaus Müller [this message]
2011-03-27 12:45 ` Richard Schütz
2011-03-27 14:45 ` Klaus Müller
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=4D8F5A37.9070306@justmail.de \
--to=kmueller@justmail.de \
--cc=linux-wireless@vger.kernel.org \
--cc=r.schtz@t-online.de \
/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.