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: 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.] [PATCH] 32bit sequence number and TTL for broadcasts
Date: Mon, 26 Apr 2010 15:55:59 +0800	[thread overview]
Message-ID: <201004261555.59856.lindner_marek@yahoo.de> (raw)
In-Reply-To: <201004252248.20341.sven.eckelmann@gmx.de>

On Monday 26 April 2010 04:48:13 Sven Eckelmann wrote:
> First thing: it doesn't compile here :( (UML), but I am quite unsure if
>  this is a UML problem like many other things or a bigger problem.... it
>  seems that it is uml specific as ATOMIC64_INIT and other thingss are
>  defined, but the implementation of specific functions are missing... but
>  this is not the first time such thing happens with uml. Maybe someone with
>  some time can check different openwrt builds.
> 
> For example other architecture seems to use the generic implementation of
>  it: * arm
>  * parisc
>  * powerpc
>  * sh

I think Sven got a point here. It seems that for atomic64_t to work one needs 
a CPU which supports 64Bit operations otherwise the linux kernel will use its 
generic implementation. Apparently it uses an array of 16 spinlocks to provide 
this functionality. I wonder whether this might be a lot of overhead for our 
needs. Furthermore the generic implementation was added recently (as far as I 
can tell 2.6.30 does not have it) which raises the question of backward 
compatibility.

Regards,
Marek

  parent reply	other threads:[~2010-04-26  7:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-25 16:51 [B.A.T.M.A.N.] [PATCH] 32bit sequence number and TTL for broadcasts Simon Wunderlich
2010-04-25 20:48 ` Sven Eckelmann
2010-04-25 22:04   ` Simon Wunderlich
2010-04-26  7:55   ` Marek Lindner [this message]
2010-04-26  8:49     ` Sven Eckelmann
2010-04-26  8:47 ` [B.A.T.M.A.N.] [PATCHv2] batman-adv: " Sven Eckelmann
2010-04-28 21:01   ` Sven Eckelmann

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=201004261555.59856.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.de \
    --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