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: Sun, 3 Apr 2011 23:25:55 +0200 [thread overview]
Message-ID: <201104032325.56687.sven@narfation.org> (raw)
In-Reply-To: <BANLkTinL7SPtofEQsacsckPqD3ySniJF_Q@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1124 bytes --]
hlabishi kobo wrote:
> int weighted_bit_packet_count(TYPE_OF_WORD *seq_bits)
> {
> int i,check, count = 0;
> TYPE_OF_WORD word;
>
> for (i = 0; i < NUM_WORDS; i++) {
> word = seq_bits[i];
> int j = WORD_BIT_SIZE, k = 1;
>
> while (j > 0 && k <= 32){
it is wrong to assume that unsigned long is 32 bit long.
> check = (word & (1 << j)) >> j;
> if (check == 1)
> count += k;
> j--;
> k++;
I would doubt that it is correct to give every set bit the same weight when
they have the the distance of sizeof(unsigned long)*8. And I cannot find a
good reason why an "old" unsigned long should get the same weights as the
"newest" unsigned long - at least not when the actual weights should be
reduced for "older" bits in a single unsigned long and the overall weights
should be monotonic decreasing with the age. And using WORD_BIT_SIZE for j is
like assuming that we only have a single unsigned long in seq_bits... which is
not true for many architectures.
And the code is overly complicated without any good reason.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-04-03 21:25 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
2011-04-03 21:10 ` hlabishi kobo
2011-04-03 21:25 ` Sven Eckelmann [this message]
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=201104032325.56687.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox