From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Marek Lindner Date: Wed, 4 Apr 2012 10:08:06 +0200 References: <1333370896-11295-1-git-send-email-martin@hundeboll.net> In-Reply-To: <1333370896-11295-1-git-send-email-martin@hundeboll.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201204041008.06362.lindner_marek@yahoo.de> Subject: Re: [B.A.T.M.A.N.] [RFC 0/2] Create counters for measuring behaviour 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 Monday, April 02, 2012 14:48:14 Martin Hundeb=C3=B8ll wrote: > Before sending an RFC on my work with network coding/catwoman, I would li= ke > some feedback on this stats-feature I build to measure the behaviour of > catwoman. >=20 > It is basically a set of counters that are incremented on various places = in > the code as a more detailed alternative to the interface statistics. >=20 > Currently, my catwoman branch uses these counters (e.g. to tell how many > packets are coded together), but other counters can easily be added. E.g. > counters relevant to the BLA, DAT, OGM/ELP code. >=20 > If this feature is unneeded/unwanted, I will remove the dependency in > catwoman. Could you explain in a few words how catwoman depends on the stats counter ? Regards, Marek