From: Felix Fietkau <nbd@openwrt.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH/RFC] ath9k PER/ratecontrol
Date: Fri, 29 Apr 2011 21:07:25 +0200 [thread overview]
Message-ID: <4DBB0C6D.7000904@openwrt.org> (raw)
In-Reply-To: <4DBABD9A.3070309@corscience.de>
On 2011-04-29 3:31 PM, Andreas Hofmann wrote:
> Hi Felix,
>
> On 29.04.2011 13:20, Felix Fietkau wrote:
>> On 2011-04-28 11:36 AM, Andreas Hofmann wrote:
>> You could try using minstrel_ht instead of the ath9k rate control.
>> People have told me that it produces much lower PER, it might help for
>> both performance and reliability of your video transmission.
>
> I did try that and it performed better than the default
> ath9k-ratecontrol, but with focus on PER, the slowed down
> ath9k-ratecontrol gave even better results. I did not inspect the
> performance regarding maximum data rate during testing, though.
What kind of PER are you looking for? Just the one in the rate control
stats, or are you getting any excessive retries during your tests?
Are you using any specific measurements in your app?
- Felix
prev parent reply other threads:[~2011-04-29 19:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 9:36 [ath9k-devel] [PATCH/RFC] ath9k PER/ratecontrol Andreas Hofmann
2011-04-28 9:36 ` [ath9k-devel] [PATCH] ath9k/rc.c: Change poll-interval to 2000 in ath9k-ratetables Andreas Hofmann
2011-04-29 7:00 ` [ath9k-devel] [PATCH/RFC] ath9k PER/ratecontrol Mohammed Shafi
2011-04-29 13:30 ` Andreas Hofmann
2011-04-29 13:36 ` Mohammed Shafi
2011-04-29 13:37 ` Mohammed Shafi
2011-04-29 7:19 ` Adrian Chadd
2011-04-29 7:21 ` Mohammed Shafi
2011-04-29 10:27 ` Adrian Chadd
2011-04-29 12:00 ` Mohammed Shafi
2011-04-29 11:20 ` Felix Fietkau
2011-04-29 13:31 ` Andreas Hofmann
2011-04-29 13:35 ` Adrian Chadd
2011-04-29 19:07 ` Felix Fietkau [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=4DBB0C6D.7000904@openwrt.org \
--to=nbd@openwrt.org \
--cc=ath9k-devel@lists.ath9k.org \
/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.