-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Robert Osfield wrote: > Hi Jan,
> Its not quite the same w.r.t single core and multi-core, on a single > core machine each thread/process gets a scheduled block on time CPU > and during this period nothing else runs, nothing else can read and > write to memory. In a multi-core system things properly happen in > parallel - so contention over reading and writing of memory become a > much greater issue, this is why its not uncommon to find > multi-threaded code that runs "robustly" on a single core breaks once > you throw more cores at it. Of course, I know that :) (I happen to a have a master in parallel and distributed systems :-p ) My point was that even on a single core machine you can get deadlock with current generation of OS-es, despite the processes not really running in parallel. The increased "robustness" is only illusory - the problem is still there, it just takes more to expose it - essentially the same thing as you have said. > I guess there is chance that is happening, but I would expect that > occasionally we'd see hangs on multi-core systems if timing was an > issue. Well, I am getting it on a dual core machine too - my Athlon is the dual one. Strange that you didn't manage to hit the problem, though. Jan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org iD8DBQFG0G92n11XseNj94gRAmDiAKDVB/vfOoBP8mCUWGGqr3M4Lh3t1wCfWpWR t8CgzDaQz2YeV7jft+oABS0= =fwsc -----END PGP SIGNATURE----- _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
