From: Bruno Randolf <br1@einfach.org>
To: sedat.dilek@gmail.com
Cc: Nick Kossifidis <mickflemm@gmail.com>,
Jonathan Guerin <jonathan@guerin.id.au>,
"ath5k-devel" <ath5k-devel@lists.ath5k.org>,
"linux-wireless" <linux-wireless@vger.kernel.org>
Subject: Re: [ath5k-devel] ath5k: Weird Retransmission Behaviour
Date: Tue, 7 Dec 2010 11:29:05 +0900 [thread overview]
Message-ID: <201012071129.05281.br1@einfach.org> (raw)
In-Reply-To: <AANLkTinKuj+e+yEwn_1g268BLPBMt71gKkUmzjbz2a3e@mail.gmail.com>
On Mon December 6 2010 19:53:49 Sedat Dilek wrote:
> >> But it seems weird that there are so many retransmissions. The default
> >> maximum numbers of retransmissions should be 7 for short frames and 4
> >> for long frames (dot11[Short|Long]RetryLimit), and this is what is set
> >> as defaults in mac80211 (local->hw.conf.short_frame_max_tx_count).
> >> Seems we are getting many
> >
> >> retransmissions from minstel, i added some debug prints:
> > When ath5k doesn't get retry limits from above it uses the following
> > defaults on dcu.
> > For now i don't think we use local->hw.conf.short_frame_max_tx_count
> > for that so the
> > default is ah_limit_tx_retries (AR5K_INIT_TX_RETRY) but seems it's
> > wrong and we should
> > fix it...
> >
> > /* Tx retry limits */
> > #define AR5K_INIT_SH_RETRY 10
> > #define AR5K_INIT_LG_RETRY AR5K_INIT_SH_RETRY
> > /* For station mode */
> > #define AR5K_INIT_SSH_RETRY 32
> > #define AR5K_INIT_SLG_RETRY AR5K_INIT_SSH_RETRY
> > #define AR5K_INIT_TX_RETRY 10
> You mean sth. like the attached patch?
Not quite. We should get the values from mac80211 and use them.
At least this does explain the resetting of the contention window after 10.
bruno
next prev parent reply other threads:[~2010-12-07 2:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 6:30 ath5k: Weird Retransmission Behaviour Jonathan Guerin
2010-12-06 8:14 ` Bruno Randolf
2010-12-06 9:36 ` [ath5k-devel] " Nick Kossifidis
2010-12-06 10:53 ` Sedat Dilek
2010-12-07 2:29 ` Bruno Randolf [this message]
2010-12-07 1:17 ` Jonathan Guerin
2010-12-08 8:06 ` Bruno Randolf
2010-12-08 8:12 ` Jonathan Guerin
2010-12-06 18:01 ` Björn Smedman
2010-12-07 1:19 ` Jonathan Guerin
2010-12-07 1:12 ` Jonathan Guerin
2010-12-07 2:34 ` Bruno Randolf
2010-12-08 16:08 ` Bob Copeland
2010-12-08 16:45 ` Bob Copeland
2010-12-08 16:56 ` John W. Linville
2010-12-08 17:06 ` Bob Copeland
2010-12-08 17:11 ` Bob Copeland
2010-12-08 17:50 ` Sedat Dilek
2010-12-08 21:36 ` Bob Copeland
2010-12-08 21:53 ` Jonathan Guerin
2010-12-09 9:21 ` Helmut Schaa
2010-12-09 12:38 ` Bob Copeland
2010-12-09 14:34 ` Jonathan Guerin
2010-12-09 17:00 ` Bob Copeland
2010-12-09 22:41 ` Jonathan Guerin
2010-12-06 9:38 ` Nick Kossifidis
2010-12-07 1:18 ` Jonathan Guerin
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=201012071129.05281.br1@einfach.org \
--to=br1@einfach.org \
--cc=ath5k-devel@lists.ath5k.org \
--cc=jonathan@guerin.id.au \
--cc=linux-wireless@vger.kernel.org \
--cc=mickflemm@gmail.com \
--cc=sedat.dilek@gmail.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).