Return-Path: From: Marek Lindner Date: Sun, 10 Oct 2010 14:53:51 +0200 References: <1286685001-15227-1-git-send-email-linus.luessing@web.de> <1286685001-15227-4-git-send-email-linus.luessing@web.de> In-Reply-To: <1286685001-15227-4-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: <201010101453.52594.lindner_marek@yahoo.de> Subject: Re: [B.A.T.M.A.N.] [PATCH 4/5] batman-adv: Make number of (re)broadcasts 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:30:00 Linus L=C3=BCssing wrote: > Depending on the scenario, people might want to adjust the number of > (re)broadcast of data packets - usually higher values in sparse or lower > values in dense networks. Is there a good reason to change this value at runtime or would a define be= =20 enough ? I just get scared when we add too many options that almost nobody= =20 cares about.=20 In other words: What is the use case ? Can we handle it by some kind of aut= o- detection ? Regards, Marek