Re: sizeof

ena8t8si@xxxxxxxxx wrote:
CBFalconer wrote:

.... snip ...

Anytime you have concurrent processes contending for resources you
can have deadlocks.

False.

If the concurrent processes are unrestricted in resource use
then there can be deadlock. But a more conservative policy
for doing resource allocation can easily avoid deadlock (and
I don't mean just in trivial ways either).

Excuse my OT post; it bugs me when broad sweeping
statements are made that aren't even approximately correct.

Read what I wrote with a modicum of care. Can have does not mean
will have.

--
Chuck F (cbfalconer@xxxxxxxxx) (cbfalconer@xxxxxxxxxxxxx)
Available for consulting/temporary embedded and systems.
<http://cbfalconer.home.att.net> USE maineline address!


.

Relevant Pages

  • Re: How to programmatically avoid deadlock?
    ... before the wait for the 'other' resource is resolved. ... splitting computation in a vat into "turns" which occur in response to ... versatile parallel programming technique helps me to ... understand that deadlock situation is fully natural, ...
    (comp.programming.threads)
  • Re: Deadlock im Recht
    ... Schön, mal wieder davon zu hören, kenn ich noch aus den Vorlesungen. ... Deadlock: ... Conditions for Resource Deadlock ... At most 1 KLT is in its CS ...
    (de.soc.recht.misc)
  • Re: Am I using ThreadPool the right way?
    ... It is possible to debug deadlocks and other threading issues in the Express version, but it's not something I'd recommend for someone unfamiliar with the general techniques of dealing with thread issues in the first place, since Express doesn't provide any direct way to get at the individual threads in the debugger. ... You'll be looking for threads that are stopped on a statement that waits for some resource, to identify which threads are involved in the deadlock and why they are waiting. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Prevents Events From Interrupting Events
    ... But since that's pretty obvious and since you're still asking the question, I'm assuming you don't have complete control over the events. ... it cannot move and I get a deadlock. ... then you also need to design your architecture so that you don't have one thread trying to get a resource another already has while that other thread is trying to get the resource the first thread already has. ... The delegate type does in fact make this potentially easier, since you can either create your own queue of delegates with an object array for the parameters and process it yourself, or take advantage of the Control.BeginInvokemethod to queue execution of delegates on a very specific thread. ...
    (microsoft.public.dotnet.languages.csharp)