All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: hlabishi kobo <hlabishik@gmail.com>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] BATMAN routing
Date: Tue, 22 Mar 2011 00:01:45 +0100	[thread overview]
Message-ID: <201103220001.48909.sven@narfation.org> (raw)
In-Reply-To: <AANLkTinPwwPP-kP9QajcgC5+90w1x-3-wc0S3MhJdF8F@mail.gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 980 bytes --]

On Monday 21 March 2011 23:40:57 hlabishi kobo wrote:
[...]
> I actually printed the seq_bits[i] and that is basically why i used 32
> but that was just for debugging purpose. But actually if i use
> NUM_WORDS, my weighted sum become very small whereas if i use 32 it
> becomes very big, trying to understand what might be causing it to be
> that way.

NUM_WORDS == amount of unsigned long/words
WORD_BIT_SIZE == amount of bits in a unsigned long
TQ_LOCAL_WINDOW_SIZE == sum of bits in seq_bits

Nothing really fancy here.

> > you only calculate the weighted sum of a single "word" (which you static
> > casted to int....?) and not all words.
> 
> i actually dont understand this very well, how many words does seq_bits[i]
> have?

a single "word"/unsigned long. seq_bits consist of NUM_WORDS words (words are 
defined in context of seq_bits as unsigned long - that's why we removed 
TYPE_OF_WORD completely and just use unsigned long).

Regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2011-03-21 23:01 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.14.1290812292.944.b.a.t.m.a.n@lists.open-mesh.org>
     [not found] ` <AANLkTimR7VU95r3C-=C9rn5ftZahKkNTu3-cU-Vft+VZ@mail.gmail.com>
2010-11-28 22:01   ` [B.A.T.M.A.N.] Fwd: BATMAN routing hlabishi kobo
2010-11-29 20:13     ` Linus Lüssing
2010-11-29 22:23       ` Linus Lüssing
2010-11-29 22:31     ` [B.A.T.M.A.N.] " hlabishi kobo
2010-11-30 17:26       ` Marek Lindner
2010-12-01  9:46       ` hlabishi kobo
2010-12-01 12:30         ` Marek Lindner
2010-12-02 10:27           ` Linus Lüssing
2010-12-02 12:02             ` Antonio Quartulli
2010-12-06 10:40               ` Daniele Furlan
2010-12-06 16:20                 ` Marek Lindner
2010-12-06 17:06                   ` Daniele Furlan
2010-12-07 10:09               ` Linus Lüssing
2010-12-11  9:51         ` hlabishi kobo
2010-12-20  9:05           ` Linus Lüssing
2011-02-24  9:58             ` hlabishi kobo
2011-02-24 10:23               ` Sven Eckelmann
2011-02-28 10:46                 ` hlabishi kobo
2011-02-28 12:03                   ` Sven Eckelmann
     [not found]                     ` <AANLkTinja_Hq4ze-fOFbHRK-iDzzA3Tk0oAsJ+CB=M2S@mail.gmail.com>
2011-02-28 19:29                       ` Sven Eckelmann
     [not found]                         ` <AANLkTikj8oj26P_F1LTiGWnt2R=29VESfpD1ZsfeL4X0@mail.gmail.com>
2011-03-08  9:52                           ` Sven Eckelmann
2011-03-17 22:40                             ` hlabishi kobo
2011-03-18 11:18                               ` Sven Eckelmann
2011-03-21 22:40                                 ` hlabishi kobo
2011-03-21 23:01                                   ` Sven Eckelmann [this message]
2011-04-03 21:10                                     ` hlabishi kobo
2011-04-03 21:25                                       ` Sven Eckelmann
2011-04-19 10:21                                         ` hlabishi kobo
2010-11-29 22:31     ` [B.A.T.M.A.N.] Fwd: " Chris Lang
2010-11-28 21:28 [B.A.T.M.A.N.] " hlabishi kobo

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=201103220001.48909.sven@narfation.org \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=hlabishik@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.