From: Christian Lamparter <chunkeey@web.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless" <linux-wireless@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH 1/2] ar9170: handle otus' A-MPDU density definitions
Date: Sat, 25 Apr 2009 12:30:10 +0200 [thread overview]
Message-ID: <200904251230.10689.chunkeey@web.de> (raw)
In-Reply-To: <1240645349.18031.52.camel@johannes.local>
On Saturday 25 April 2009 09:42:29 Johannes Berg wrote:
> On Fri, 2009-04-24 at 21:35 +0200, Christian Lamparter wrote:
> > + .ampdu_factor = 3, \
> > + .ampdu_density = 6, \
>
> FWIW, I also tried some varying values. This should indicate what you're
> able to receive though, not what you're able to transmit since you
> control that anyway.
yeah... in fact the _correct_ value according to otus is 0 (unrestricted),
however that's a bit hard to believe... and ath9k's (not the same
mac... I know) default works rather well.
[I see about 65 Mbits sustainable throughput and peaks in the lower 80.]
> I think we currently don't have a setting though for what to transmit with...
> this might need to be added somewhere depending on the RA.
well, there should be a table or some bits in phy_control for this purpose...
But it looks like otus only has this single MAC knob and the safest setting
otus allows is 7 = 8us...
of course it would be nice if ieee80211_bss_ht_conf in bss_conf, could be
replaced by ieee80211_sta_ht_cap which has the necessary elements.
after all this chip was designed as a client adapter, so there's no need
to handle multiple a-mpdu density at the same time...
Regards,
Chr
prev parent reply other threads:[~2009-04-25 10:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 19:35 [PATCH 1/2] ar9170: handle otus' A-MPDU density definitions Christian Lamparter
2009-04-25 7:42 ` Johannes Berg
2009-04-25 10:30 ` Christian Lamparter [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=200904251230.10689.chunkeey@web.de \
--to=chunkeey@web.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).