public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
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 0/3] GSOC 2012: bandwidth meter project
Date: Fri, 10 Aug 2012 15:44:10 +0200	[thread overview]
Message-ID: <20120810134409.GA18045@pandem0nium> (raw)
In-Reply-To: <1344514526-30256-1-git-send-email-montik@autistici.org>

[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]

Hello Edo,

as discussed already, some general remarks:

 * please squash these patches to one - as far as I can see, the 2 others are mostly
   fixes to the first one
 * Don't turn on debugging in the Makefile - we don't want that by default
 * please also include the batctl patch, it is important for testing

Thanks
	Simon

On Thu, Aug 09, 2012 at 02:15:23PM +0200, Edo Monticelli wrote:
> Hi,
> 
> I have almost completed my Google Summer of Code project and I'd like to have a
> feedback from the batman community. The project is a kernel-space bandwidth
> meter, a lightweight tool to measure network performance between batman nodes.
> You can find a general project description in the project wiki page:
> 
> http://www.open-mesh.org/projects/batman-adv/wiki/GSOC2012_BW
> 
> Any advice is welcome,
> Edo Monticelli
> 
> 
> Edo Monticelli (3):
>   batman-adv: bandwidth meter implementation
>   batman-adv: sender retransmission counter
>   batman-adv: seqnumber is wrap around safe
> 
>  Makefile         |    2 +-
>  Makefile.kbuild  |    1 +
>  bw_meter.c       |  531 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
>  bw_meter.h       |    7 +
>  icmp_socket.c    |   18 ++
>  main.c           |    2 +
>  packet.h         |   22 ++-
>  routing.c        |   15 ++-
>  soft-interface.c |    5 +
>  types.h          |   38 ++++
>  10 files changed, 634 insertions(+), 7 deletions(-)
>  create mode 100644 bw_meter.c
>  create mode 100644 bw_meter.h
> 
> -- 
> 1.7.8.6
> 
> 

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      parent reply	other threads:[~2012-08-10 13:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-09 12:15 [B.A.T.M.A.N.] [RFC 0/3] GSOC 2012: bandwidth meter project Edo Monticelli
2012-08-09 12:15 ` [B.A.T.M.A.N.] [RFC 1/3] batman-adv: bandwidth meter implementation Edo Monticelli
2012-08-12 12:20   ` Sven Eckelmann
2012-08-13  9:07     ` Sven Eckelmann
2012-08-13  9:14   ` Sven Eckelmann
2012-08-09 12:15 ` [B.A.T.M.A.N.] [RFC 2/3] batman-adv: sender retransmission counter Edo Monticelli
2012-08-09 12:15 ` [B.A.T.M.A.N.] [RFC 3/3] batman-adv: seqnumber is wrap around safe Edo Monticelli
2012-08-10 13:44 ` Simon Wunderlich [this message]

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=20120810134409.GA18045@pandem0nium \
    --to=simon.wunderlich@s2003.tu-chemnitz.de \
    --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