From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Jean-Pierre TOSONI <jp.tosoni@acksys.fr>,
Ben Greear <greearb@candelatech.com>,
SEDE <s.deronne@televic.com>,
Benjamin Beichler <Benjamin.Beichler@uni-rostock.de>,
ath10k <ath10k@lists.infradead.org>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>
Subject: RE: Setting tx retry count in ath10k
Date: Wed, 18 Jul 2018 20:27:17 +0200 [thread overview]
Message-ID: <871sc05ri2.fsf@toke.dk> (raw)
In-Reply-To: <AM4PR0101MB230575D91CEE21630A723466E4530@AM4PR0101MB2305.eurprd01.prod.exchangelabs.com>
Jean-Pierre TOSONI <jp.tosoni@acksys.fr> writes:
> @Toke: As you can see in the patch, the value 30 was the fixed value
> defined in ath9k, I kept it for compatibility only (and that's why I
> wanted to make it configurable :-)
Yup, I'm aware that this is the default from ath9k; doesn't make it any
less wrong ;)
> On another hand, Minstrel in mac80211 seems to vary retries according
> to what you say, i.e. Minstrel tries to stay below a certain amount of
> time, but this only applies to short/long retries.
Right, haven't had time to poke into what exactly Minstrel does; have
just observed that it sometimes runs really long. But for most cases
it's not too bad...
-Toke
next prev parent reply other threads:[~2018-07-18 19:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 0:37 Setting tx retry count in ath10k Ben Greear
2018-07-17 7:39 ` Benjamin Beichler
2018-07-17 7:56 ` SEDE
2018-07-17 15:07 ` Ben Greear
2018-07-18 15:50 ` Jean-Pierre TOSONI
2018-07-18 16:00 ` Ben Greear
2018-07-18 16:21 ` Toke Høiland-Jørgensen
2018-07-18 17:01 ` Jean-Pierre TOSONI
2018-07-18 18:27 ` Toke Høiland-Jørgensen [this message]
2018-07-19 12:39 ` Benjamin Beichler
2018-07-19 13:21 ` Ben Greear
2018-07-19 13:48 ` Toke Høiland-Jørgensen
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=871sc05ri2.fsf@toke.dk \
--to=toke@toke.dk \
--cc=Benjamin.Beichler@uni-rostock.de \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
--cc=jp.tosoni@acksys.fr \
--cc=linux-wireless@vger.kernel.org \
--cc=s.deronne@televic.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).