RE: race condition?

I think the best approach is to not let it migrate home (or elsewhere) until
the outstanding syscall(s) have been answered. 

 Moshe

-----Original Message-----
From: openmosix-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
[mailto:openmosix-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of Matt Dew
Sent: Monday, May 08, 2006 11:00 AM
To: openMosix-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: [email protected]
Subject: [Openmosix-devel] race condition?

(I'm having trouble sending to the list and have been asked to resend so I
apologize if you've received this message several times.)

Hi Tab, et al,
 What are the thoughts on the condition where the remote node sends a
syscall back to the home node and then receives a migrate home command
before the syscall response?   Is this the same problem (out of
sync-ness) that is causing the received -32 of 8 errors?

What is the best way to fix this?  
 1) Put in some ack/nack commands to ensure both remote and deputy are in
the same place?
 2) Open two ports. One for migration stuff and another for syscalls?
 3) Modify the functions to handle these cases?
 4) Add a counter field to the structs for bookkeeping; so both remote and
deputy know which response goes with which command and then merge the
calling functions?
 5) I'm simply not seeing the logic that is already supposed to handle
these?

I'm hoping it's 5, but if it's not;
3 seems like a bad idea and will probably not scale well.  2 might scale the
best and be most robust??

The simple attached program shows it reliably.  It'll crash when trying to
migate back home.

Matt 



-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642