From: Sven Eckelmann <sven.eckelmann@gmx.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] Batman gateway lock ups
Date: Wed, 10 Sep 2008 11:50:36 +0200 [thread overview]
Message-ID: <200809101150.41328.sven.eckelmann@gmx.de> (raw)
In-Reply-To: <200809100045.18090.sven.eckelmann@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]
On Wednesday 10 September 2008 00:45:07 Sven Eckelmann wrote:
> [...]
> /* v0 and v1 holds pointer to new allocated struct */
> /* a3 holds "zero" - like t0 */
> 9a8: sw s1,8(v0) /* store pointer to client_data in new data buffer */
> 9ac: lw v0,36(a3) /* v0 gets free_client_list.next -> lets call it
> next_element */
> /* shouldn't be another instruction between load and usage of the
> register? - like a nop */
> 9b0: sw v0,0(v1) /* store next_element in tmp_entry.list.next */
> 9b4: sw v1,4(v0) /* store pointer to tmp_entry next_element.prev */
> 9b8: sw v1,36(a3) /* store pointer to tmp_entry in freeclient_list.next
> */
> 9bc: j 9d4 <cleanup_module+0x524>
> 9c0: sw t0,4(v1) /* saves freeclient_list in tmp_entry.prev << if this
> would not be executed in parallel, we would get
> wrong data here, but because we are using mips it
> must be executed */
> [...]
Ok, searched inside the official mips32 instruction set reference and both
questionable instructions are defined in a hard way without any unpredictable
or undefined remarks. So they should be working fine.
Best regards
Sven Eckelmann
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-09-10 9:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 15:01 [B.A.T.M.A.N.] Batman gateway lock ups Outback Dingo
2008-09-08 7:08 ` Sven Eckelmann
2008-09-08 21:18 ` Sven Eckelmann
2008-09-08 21:45 ` Sven Eckelmann
2008-09-09 8:03 ` Sven Eckelmann
2008-09-09 11:26 ` Simon Wunderlich
2008-09-09 22:45 ` Sven Eckelmann
2008-09-10 9:50 ` Sven Eckelmann [this message]
2009-07-21 20:48 ` Simon Wunderlich
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=200809101150.41328.sven.eckelmann@gmx.de \
--to=sven.eckelmann@gmx.de \
--cc=b.a.t.m.a.n@open-mesh.net \
/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