From: ferran <ranker72@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: [question] Rate control algorithm for mesh
Date: Mon, 16 Nov 2015 17:02:39 +0100 [thread overview]
Message-ID: <5649FE1F.4060203@gmail.com> (raw)
Hello everybody,
I would like to know if there is a transmit rate control algorithm out
there that takes into account the destination MAC address. My setting is
like this:
[node0]· · · · ·[node1]············[node2]
Where the spaced pattern means a poor connection and the densely dotted
pattern means a good connection.
The problem here is that node1 oscillates between fast rates and slow
rates, as when transmitting to node0 it must reduce the rate, and when
transmitting to node2 it increases the rate since it must take profit of
the channel. I am therefore getting many re-tx between n1 and n0, and
n1-->n2 isn't as fast as it could.
Currently I am using the PID-based RC, but I'm afraid that this problem
isn't adressed at Minstrel neither.
Am I wrong?
Thank you for your excellent work!
Ferran
next reply other threads:[~2015-11-16 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 16:02 ferran [this message]
2015-11-16 18:16 ` [question] Rate control algorithm for mesh Felix Fietkau
2015-11-19 16:21 ` ferran
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=5649FE1F.4060203@gmail.com \
--to=ranker72@gmail.com \
--cc=linux-wireless@vger.kernel.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 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).