From: Antonio Quartulli <ordex@autistici.org>
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.] [PATCHv2 5/5] batman-adv: Allow to use different sized hash locks array
Date: Sat, 1 Dec 2012 17:40:45 +0100 [thread overview]
Message-ID: <20121201164044.GO24115@ritirata.org> (raw)
In-Reply-To: <1353931112-17392-5-git-send-email-sven@narfation.org>
[-- Attachment #1: Type: text/plain, Size: 2008 bytes --]
On Mon, Nov 26, 2012 at 12:58:32PM +0100, Sven Eckelmann wrote:
> The amount of locks of a hash directly affects the parallelity when all access
> independent parts of the hash. But this also affects the amount of memory used
> for each hash. Allowing to decouple the hash size and the lock size allows to
> reduce this memory consumption for hashes which don't allow this parallelism.
>
> Signed-off-by: Sven Eckelmann <sven@narfation.org>
> ---
> bridge_loop_avoidance.c | 28 ++++++++++++++--------------
> distributed-arp-table.c | 16 ++++++++--------
> distributed-arp-table.h | 6 +++---
> hash.h | 19 +++++++++----------
> originator.c | 6 ++++--
> originator.h | 13 +++++--------
> translation-table.c | 22 ++++++++++++++--------
> vis.c | 8 ++++----
> 8 files changed, 61 insertions(+), 57 deletions(-)
>
> diff --git a/bridge_loop_avoidance.c b/bridge_loop_avoidance.c
> index 1a78bac..781119f 100644
> --- a/bridge_loop_avoidance.c
> +++ b/bridge_loop_avoidance.c
> @@ -38,7 +38,7 @@ static void batadv_bla_send_announce(struct batadv_priv *bat_priv,
> struct batadv_backbone_gw *backbone_gw);
>
> /* return the index of the claim */
> -static inline uint32_t batadv_choose_claim(const void *data, uint32_t size)
> +static inline uint32_t batadv_choose_claim(const void *data)
> {
> struct batadv_claim *claim = (struct batadv_claim *)data;
> uint32_t hash;
> @@ -46,12 +46,11 @@ static inline uint32_t batadv_choose_claim(const void *data, uint32_t size)
> hash = jhash(&claim->addr, sizeof(claim->addr), 0);
> hash = jhash(&claim->vid, sizeof(claim->vid), hash);
>
> - return hash % size;
> + return hash;
I do not fully understand how having the mod operation inside the function would
prevent the decoupling. Why you need to move it out?
Cheers,
--
Antonio Quartulli
..each of us alone is worth nothing..
Ernesto "Che" Guevara
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-12-01 16:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 11:58 [B.A.T.M.A.N.] [PATCHv2 1/5] batman-adv: Use common Jenkins Hash implementation Sven Eckelmann
2012-11-26 11:58 ` [B.A.T.M.A.N.] [PATCHv2 2/5] batman-adv: Define the size of hashtables by hash bits Sven Eckelmann
2012-11-26 11:58 ` [B.A.T.M.A.N.] [PATCHv2 3/5] batman-adv: Remove size information from hash table Sven Eckelmann
2012-11-26 11:58 ` [B.A.T.M.A.N.] [PATCHv2 4/5] batman-adv: Remove wrapper structure for hash tables Sven Eckelmann
2012-11-26 11:58 ` [B.A.T.M.A.N.] [PATCHv2 5/5] batman-adv: Allow to use different sized hash locks array Sven Eckelmann
2012-12-01 16:40 ` Antonio Quartulli [this message]
2012-12-01 16:58 ` Sven Eckelmann
2012-12-01 17:07 ` Antonio Quartulli
2012-12-24 14:25 ` [B.A.T.M.A.N.] [PATCHv2 1/5] batman-adv: Use common Jenkins Hash implementation Pau Koning
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=20121201164044.GO24115@ritirata.org \
--to=ordex@autistici.org \
--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