From: Andrew Lunn <andrew@lunn.ch>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] [RFC] ELP
Date: Fri, 23 Mar 2012 07:32:06 +0100 [thread overview]
Message-ID: <20120323063206.GA5662@lunn.ch> (raw)
In-Reply-To: <201203222250.31309.lindner_marek@yahoo.de>
On Fri, Mar 23, 2012 at 05:50:30AM +0800, Marek Lindner wrote:
>
> Hi,
>
> after numerous infrastructure changes in the past weeks ELP[1] slowly
> approaches the state in which it can be tested and later merged into the
> master branch.
Hi Marek
Great to see this work going forward.
Something that Linus and I discussed was using unicast packets as
well. We didn't do anything at the time, project deadlines looming
etc... It is also a while ago, so maybe i'm remembering this wrong...
The problem with broadcasting the ELP packets is that they are always
sent with the most robust coding rate. So ELP gives you an idea how
good the 1Mbps broadcast channel is, not how good the unicast channel
the automatic rate selection algorithm is using is. I think we
discussed mixing in some unicast packets in the forward direction. The
ELP packets containing the reports would stay the same, and so
function as node detection. But a node could also send out unicast ELP
packets to its known neighbours and they would be included into the
LQ.
There are obvious drawbacks. More overhead, especially in dense
networks. It is also not clear if the measurements would be
better. Unicast packets get a number of retries with fast ACKs, where
as multicast does not. So multicast might actually give a better
measure of the link at 1Mbps.
Do you know if Linus had chance to explore these ideas during his
GSOC?
Thanks
Andrew
next prev parent reply other threads:[~2012-03-23 6:32 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 21:50 [B.A.T.M.A.N.] [RFC] ELP Marek Lindner
2012-03-22 21:51 ` [B.A.T.M.A.N.] [RFC 1/5] batman-adv: ELP - adding basic infrastructure Marek Lindner
2012-03-22 21:51 ` [B.A.T.M.A.N.] [RFC 2/5] batman-adv: ELP - creating neighbor structures, updating LQs Marek Lindner
2012-03-23 20:52 ` Andrew Lunn
2012-04-05 19:59 ` Marek Lindner
2012-03-23 21:22 ` Andrew Lunn
2012-03-24 8:14 ` Antonio Quartulli
2012-03-24 20:21 ` Andrew Lunn
2012-04-05 20:11 ` Marek Lindner
2012-04-06 7:17 ` Andrew Lunn
2012-04-06 8:18 ` Marek Lindner
2012-04-05 20:08 ` Marek Lindner
2012-03-22 21:51 ` [B.A.T.M.A.N.] [RFC 3/5] batman-adv: ELP - exporting neighbor list via debugfs Marek Lindner
2012-03-22 21:51 ` [B.A.T.M.A.N.] [RFC 4/5] batman-adv: ELP - adding sysfs parameter for elp interval Marek Lindner
2012-03-22 21:51 ` [B.A.T.M.A.N.] [RFC 5/5] batman-adv: ELP - add configurable minimum ELP packet length (def: 300B) Marek Lindner
2012-03-24 20:39 ` Andrew Lunn
2012-04-05 20:19 ` Marek Lindner
2012-03-23 6:41 ` [B.A.T.M.A.N.] [RFC 1/5] batman-adv: ELP - adding basic infrastructure Andrew Lunn
2012-03-23 6:50 ` Andrew Lunn
2012-04-05 20:21 ` Marek Lindner
2012-03-23 6:32 ` Andrew Lunn [this message]
2012-03-23 7:50 ` [B.A.T.M.A.N.] [RFC] ELP Antonio Quartulli
2012-04-05 20:30 ` Marek Lindner
2012-04-06 9:13 ` Andrew Lunn
2012-04-06 16:57 ` dan
2012-04-06 17:19 ` Andrew Lunn
2012-04-06 18:04 ` dan
2012-03-23 6:34 ` Andrew Lunn
2012-03-23 7:51 ` Antonio Quartulli
2012-04-05 20:30 ` Marek Lindner
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=20120323063206.GA5662@lunn.ch \
--to=andrew@lunn.ch \
--cc=b.a.t.m.a.n@lists.open-mesh.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