From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Marek Lindner Date: Sun, 10 Oct 2010 14:49:51 +0200 References: <1286685001-15227-1-git-send-email-linus.luessing@web.de> <1286685001-15227-3-git-send-email-linus.luessing@web.de> In-Reply-To: <1286685001-15227-3-git-send-email-linus.luessing@web.de> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201010101449.52124.lindner_marek@yahoo.de> Subject: Re: [B.A.T.M.A.N.] [PATCH 3/5] batman-adv: Make hop_penalty configurable via sysfs Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking List-Id: The list for a Better Approach To Mobile Ad-hoc Networking List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: The list for a Better Approach To Mobile Ad-hoc Networking On Sunday 10 October 2010 06:29:59 Linus L=C3=BCssing wrote: > When having a mixed topology of both very mobile and rather static > nodes, you are usually best advised to set the originator interval on > all nodes to a level best suited for the most mobile node. >=20 > However, if most of the nodes are rather static, this can create a lot > of undesired overhead as a trade-off then. If setting the interval too > low on the static nodes, a mobile node might be chosen as a router for > too long, not switching away from it fast enough because of its > mobility and the low frequency of ogms of static nodes. Any good reason for all these "originator interval" explanations here ? > @@ -592,6 +592,7 @@ struct net_device *softif_create(char *name) > atomic_set(&bat_priv->gw_mode, GW_MODE_OFF); > atomic_set(&bat_priv->gw_class, 0); > atomic_set(&bat_priv->orig_interval, 1000); > + atomic_set(&bat_priv->hop_penalty, 30); Either you initialize the value with TQ_HOP_PENALTY or you remove the defin= e=20 from the main.h file. Regards, Marek