From: Marek Lindner <mareklindner@neomailbox.ch>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Sven Eckelmann <sven@narfation.org>,
Ligang LIU <heishuihe2008@163.com>,
a@unstable.cc
Subject: Re: [B.A.T.M.A.N.] Recent test result. Re:Re: Paper "Performance Evaluation of BATMAN-adv Wireless Mesh Network Routing Algorithms "
Date: Fri, 31 Aug 2018 20:16:31 +0800 [thread overview]
Message-ID: <2087861.tpEfN19RDO@rousseau> (raw)
In-Reply-To: <3991773.ZLWj8GO7DM@bentobox>
[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]
On Friday, 31 August 2018 18:30:00 HKT Sven Eckelmann wrote:
> > I noticed 2 macro definitons.
> > #define BATADV_ELP_PROBES_PER_NODE 2
> > #define BATADV_ELP_MIN_PROBE_SIZE 200 /* bytes */
> > I wonder why it sends 2 prob ELP packets to each neighbour.
> > Can I change the value of BATADV_ELP_PROBES_PER_NODE from 2 to 1?
> > And can I decrease ELP prob packet size from 200 to 100, in order to
> > decrase the ELP airtime?
> @Antonio, @Marek: Maybe you can explain it better than me.
>
> I would guess that Antonio wanted to make sure that the rate control
> algorithm of the driver probes enough and thus provides a more realistic
> expected throughput.
Feel free to change these values to test if this has any impact. As far as I
am aware, these number are the result of an educated guess based on how
minstrel works. Antonio can shed more light on this.
> And you can just use elp_interval [2] to reduce the number of times
> broadcast and unicast ELP frames are transmitted.
I don't think unicast ELP were supposed to be affected by changing the
elp_interval. Smells like a bug to me. Antonio ?
Cheers,
Marek
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-08-31 12:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-04 11:38 [B.A.T.M.A.N.] Paper "Performance Evaluation of BATMAN-adv Wireless Mesh Network Routing Algorithms " Sven Eckelmann
2018-08-04 14:39 ` jmh8
2018-08-04 15:34 ` Sven Eckelmann
2018-08-11 6:47 ` jmh8
[not found] ` <2018081310240755548768@mail.sim.ac.cn>
2018-08-13 7:40 ` Sven Eckelmann
2018-08-30 7:50 ` [B.A.T.M.A.N.] Recent test result. " Ligang LIU
2018-08-30 8:17 ` Sven Eckelmann
2018-08-30 8:55 ` Ligang LIU
2018-08-30 9:06 ` Sven Eckelmann
2018-08-31 9:52 ` Ligang LIU
2018-08-31 10:30 ` Sven Eckelmann
2018-08-31 10:41 ` Sven Eckelmann
2018-08-31 12:16 ` Marek Lindner [this message]
2018-09-01 9:33 ` Antonio Quartulli
2018-09-01 9:08 ` Sven Eckelmann
2018-09-03 4:03 ` [B.A.T.M.A.N.] mcast_rate setting of wifi interface has significant effect to performance of V. " Ligang LIU
2018-09-03 6:25 ` Sven Eckelmann
[not found] ` <aa797db.cdf1.165a3d64b19.Coremail.heishuihe2008@163.com>
2018-09-04 10:34 ` Sven Eckelmann
2018-09-05 17:40 ` Sven Eckelmann
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=2087861.tpEfN19RDO@rousseau \
--to=mareklindner@neomailbox.ch \
--cc=a@unstable.cc \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=heishuihe2008@163.com \
--cc=sven@narfation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.