From: Felix Fietkau <nbd@openwrt.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Fixing the rate and rate relationship to OFDM
Date: Thu, 28 Mar 2013 20:00:40 +0100 [thread overview]
Message-ID: <51549358.90603@openwrt.org> (raw)
In-Reply-To: <800E57B7-01E9-4239-AD8E-FE3E1058650E@aim.com>
On 2013-03-27 7:49 PM, John Clark wrote:
> Many people seem to desire the bit rate to be the 'highest possible',
> and have that automagically set.
What's wrong with the current behavior of picking the rate that causes
the least wasted airtime?
> For some applications, I like to be able to set a specific bit rate,
> and have that bit rate used no matter the resulting errors.
That can be quite problematic with 802.11n aggregation. Any frame
transmission that has failed after too many retries causes a BlockAck
Request to be sent, which can cause other (potentially unrelated) frames
to be dropped on the receiver side.
Why do you want to do this at all?
> I have looked a the code briefly, and it seems that there is the
> possibility for setting up several retries, with changes in bit
> rate.
>
> So, the questions are:
>
> 1) how to 'fix' a rate, disable adjustments on retries, etc?
To do this per application, you'd have to put some ugly hacks into
various layers.
> 2) What is the relationship between the bit rate selected at this OS level,
> and the subcarrier modulation of the RF signal?
The standard describes what modulations are used for specific bitrates.
- Felix
next prev parent reply other threads:[~2013-03-28 19:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 18:49 [ath9k-devel] Fixing the rate and rate relationship to OFDM John Clark
2013-03-28 11:32 ` shinnazar
2013-03-28 17:45 ` John Clark
2013-03-28 18:19 ` Adrian Chadd
2013-03-28 19:29 ` John Clark
2013-03-28 19:58 ` Adrian Chadd
2013-04-02 13:04 ` Holger Schurig
2013-04-02 14:57 ` Adrian Chadd
2013-04-02 18:15 ` John Clark
2013-04-02 20:08 ` Adrian Chadd
2013-04-02 23:05 ` Jerald A DeLong
2013-04-02 23:35 ` Adrian Chadd
2013-04-02 13:51 ` Peter Stuge
2013-04-02 14:55 ` Adrian Chadd
2013-04-02 16:43 ` Peter Stuge
2013-04-02 16:49 ` Adrian Chadd
2013-04-02 17:03 ` Peter Stuge
2013-04-02 17:38 ` John Clark
2013-03-29 5:23 ` Alex Hacker
2013-03-29 17:10 ` John Clark
2013-03-29 17:47 ` Adrian Chadd
2013-03-30 12:32 ` Alex Hacker
2013-03-30 13:27 ` Adrian Chadd
2013-03-30 15:03 ` Alex Hacker
2013-03-30 15:20 ` Alex Hacker
2013-04-01 8:14 ` Alex Hacker
2013-04-01 21:29 ` Adrian Chadd
2013-03-28 19:00 ` Felix Fietkau [this message]
2013-03-28 19:32 ` John Clark
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=51549358.90603@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.