public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <lindner_marek@yahoo.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: "Martin Hundebøll" <martin@hundeboll.net>
Subject: Re: [B.A.T.M.A.N.] [PATCHv4 2/6] batman-adv: Detect coding nodes and remove these after timeout
Date: Tue, 29 Jan 2013 23:33:50 +0800	[thread overview]
Message-ID: <201301292333.50455.lindner_marek@yahoo.de> (raw)
In-Reply-To: <1359108763-31846-3-git-send-email-martin@hundeboll.net>

On Friday, January 25, 2013 18:12:39 Martin Hundebøll wrote:
> To use network coding efficiently, a relay must know when neighbor nodes
> are likely to have enough information to be able to decode a network
> coded packet. This is detected by using OGMs from batman-adv to discover
> when one neighbor is in range of another neighbor. The relay check the
> TLL to detect when an OGM is forwarded from one neighbor by another
> neighbor, and thereby knows that the two neighbors are in range and thus
> overhear packets sent by each other.
> 
> This information is saved in the orig_node struct to be used when
> searching for coding opportunities. Two lists are added to the
> orig_node struct: One for neighbors that can hear the orig_node
> (outgoing nc_nodes) and one for neighbors that the orig_node can hear
> (incoming nc_nodes).
> 
> Information about nc_nodes is kept for 10 seconds and is available
> through debugfs in batman_adv/nc_nodes to use when debugging network
> coding.
> 
> Signed-off-by: Martin Hundebøll <martin@hundeboll.net>
> ---
> v3:
>  * Fixed typos in kernel doc
> v4:
>  * Added missing kernel doc entry for struct batadv_priv_nc
> 
>  bat_iv_ogm.c     |   5 +
>  debugfs.c        |  18 +++
>  main.h           |   2 +
>  network-coding.c | 416
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++ network-coding.h
> |  47 +++++++
>  originator.c     |   6 +
>  types.h          |  32 +++++
>  7 files changed, 526 insertions(+)

Applied in revision 3ed7ada.

Thanks,
Marek

  reply	other threads:[~2013-01-29 15:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-25 10:12 [B.A.T.M.A.N.] [PATCHv4 0/6] CATWOMAN: Network coding in batman-adv Martin Hundebøll
2013-01-25 10:12 ` [B.A.T.M.A.N.] [PATCHv4 1/6] batman-adv: Add the initial code for network coding Martin Hundebøll
2013-01-29 15:33   ` Marek Lindner
2013-01-25 10:12 ` [B.A.T.M.A.N.] [PATCHv4 2/6] batman-adv: Detect coding nodes and remove these after timeout Martin Hundebøll
2013-01-29 15:33   ` Marek Lindner [this message]
2013-01-25 10:12 ` [B.A.T.M.A.N.] [PATCHv4 3/6] batman-adv: Buffer unicast packets before forward Martin Hundebøll
2013-01-29 15:35   ` Marek Lindner
2013-01-25 10:12 ` [B.A.T.M.A.N.] [PATCHv4 4/6] batman-adv: Code and transmit packets if possible Martin Hundebøll
2013-01-29 15:35   ` Marek Lindner
2013-01-25 10:12 ` [B.A.T.M.A.N.] [PATCHv4 5/6] batman-adv: Save overheard and tx packets for decoding Martin Hundebøll
2013-01-29 15:36   ` Marek Lindner
2013-01-25 10:12 ` [B.A.T.M.A.N.] [PATCHv4 6/6] batman-adv: Receive coded packets and decode them Martin Hundebøll
2013-01-29 15:36   ` Marek Lindner

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=201301292333.50455.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=martin@hundeboll.net \
    /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