public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <mareklindner@neomailbox.ch>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Sven Eckelmann <sven@narfation.org>
Subject: Re: [B.A.T.M.A.N.] [PATCHv3] batman-adv: Use common Jenkins Hash implementation
Date: Sun, 01 Mar 2015 17:17:50 +0800	[thread overview]
Message-ID: <4026910.3ENWfGA5H1@voltaire> (raw)
In-Reply-To: <1425199578-6392-1-git-send-email-sven@narfation.org>

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

On Sunday, March 01, 2015 09:46:18 Sven Eckelmann wrote:
> An unoptimized version of the Jenkins one-at-a-time hash function is used
> and partially copied all over the code wherever an hashtable is used.
> Instead the optimized version shared between the whole kernel should be
> used to reduce code duplication and use better optimized code.
> 
> Only the DAT code must use the old implementation because it is used as
> distributed hash function which has to be common for all nodes.
> 
> Signed-off-by: Sven Eckelmann <sven@narfation.org>
> ---
> v3: rebased on top of current master
> 
>  bridge_loop_avoidance.c | 16 ++++------------
>  distributed-arp-table.c | 17 +++++++++++++++--
>  hash.h                  | 22 ----------------------
>  main.h                  |  1 +
>  network-coding.c        | 10 ++--------
>  originator.h            | 13 +------------
>  translation-table.c     |  8 ++------
>  7 files changed, 25 insertions(+), 62 deletions(-)

Applied in revision 3606e0a.

Thanks,
Marek

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

      parent reply	other threads:[~2015-03-01  9:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-01  8:46 [B.A.T.M.A.N.] [PATCHv3] batman-adv: Use common Jenkins Hash implementation Sven Eckelmann
2015-03-01  9:09 ` Gio
2015-03-01  9:13   ` Sven Eckelmann
2015-03-01  9:17 ` Marek Lindner [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=4026910.3ENWfGA5H1@voltaire \
    --to=mareklindner@neomailbox.ch \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=sven@narfation.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