From: Roberto Riggio <roberto.riggio@create-net.org>
To: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Use case for the radiotap rate patch
Date: Sun, 21 Nov 2010 11:47:53 +0100 [thread overview]
Message-ID: <4CE8F8D9.1020201@create-net.org> (raw)
In the following thread Pavel was sacking for an use case for his patch to
support the radiotap rate field;
http://thread.gmane.org/gmane.linux.kernel.wireless.general/52229/focus=52265
I'm currently using the patch in a custom routing protocol for wireless mesh
networking (www.wing-project.org). The protocol uses broadcast frames sent
at rates different from the baserate in order to implement its routing
metric
(WCETT). Without the patch I would be forced to sample each neighbor using
unicast frames making the metric implementation not scalable with the number
of nodes.
Also, which would be the way to support the multi-rate retry chain from
user-space?
I'm currently playing with some custom RC algorithms in users space
using the
click modular router, but I cannot take advantage of the mrr.
thanks
R.
next reply other threads:[~2010-11-21 10:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-21 10:47 Roberto Riggio [this message]
2010-11-22 15:39 ` Use case for the radiotap rate patch Johannes Berg
2010-11-22 18:00 ` Roberto Riggio
2010-11-22 18:01 ` Johannes Berg
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=4CE8F8D9.1020201@create-net.org \
--to=roberto.riggio@create-net.org \
--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).