From: shinnazar <seytnazarovsho@ynu.ac.kr>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Fixing the rate and rate relationship to OFDM
Date: Thu, 28 Mar 2013 20:32:37 +0900 [thread overview]
Message-ID: <000001ce2ba7$f401e220$dc05a660$@ac.kr> (raw)
In-Reply-To: <800E57B7-01E9-4239-AD8E-FE3E1058650E@aim.com>
You should look at minstrel_ht code. there you can set specific rate at all
retry stages. But I think you should care about the error level, because
high error rates decreases Aggregate frame length consequently shows very
little throughput that may be not tolerable for your application.
Shinnazar
-----Original Message-----
From: John Clark [mailto:jeclark2006 at aim.com]
Sent: Thursday, March 28, 2013 3:49 AM
To: ath9k-devel at lists.ath9k.org
Subject: [ath9k-devel] Fixing the rate and rate relationship to OFDM
Many people seem to desire the bit rate to be the 'highest possible', and
have that automagically set.
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.
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?
2) What is the relationship between the bit rate selected at this OS level,
and the subcarrier modulation of the RF signal?
Thanks,
John Clark.
_______________________________________________
ath9k-devel mailing list
ath9k-devel at lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
next prev parent reply other threads:[~2013-03-28 11:32 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 [this message]
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
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='000001ce2ba7$f401e220$dc05a660$@ac.kr' \
--to=seytnazarovsho@ynu.ac.kr \
--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.