|
From: | Michael Hennebry |
Subject: | RE: [Help-glpk] GLPK re-endrant |
Date: | Thu, 2 Jul 2009 14:16:46 -0500 (CDT) |
User-agent: | Alpine 1.00 (DEB 882 2007-12-20) |
On Thu, 2 Jul 2009, Giampaolo Tomassoni wrote:
-----Original Message----- From: address@hidden [mailto:help- address@hidden On Behalf Of Michael Hennebry Sent: Thursday, July 02, 2009 5:17 PM To: Nigel Galloway Cc: address@hidden Subject: Re: [Help-glpk] GLPK re-endrant The reentrancy issue could be obviated by running GLPK instances in separate processes.Nevertheless, most of the software around nowadays is meant to be run by multi-cored CPUs. So, reentrancy actually seems to me something very close to a requisite. The GLPK team will surely have to face it ASAP.
One can run multiple processes on multi-cored CPUs. Shared memory isn't necessarily all that great a model, but is difficult to avoid with threads. Separate processes with explicit message-passing can be a lot easier to wrap one's brain around. The lack of a common address space makes it hard for them to tromp on each others data. -- Michael address@hidden "Pessimist: The glass is half empty. Optimist: The glass is half full. Engineer: The glass is twice as big as it needs to be."
[Prev in Thread] | Current Thread | [Next in Thread] |