Talk:Deadlock prevention algorithms

This article is within the scope of WikiProject Computer science, a collaborative effort to improve the coverage of Computer science related articles on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.Computer scienceWikipedia:WikiProject Computer scienceTemplate:WikiProject Computer scienceComputer science

???

This article has not yet received a rating on Wikipedia's content assessment scale.

???

This article has not yet received a rating on the project's importance scale.

Things you can help WikiProject Computer science with:

Here are some tasks awaiting attention:

Article requests :
- Requested articles/Applied arts and sciences/Computer science, computing, and Internet
Cleanup :
- Computer science articles needing attention
- Computer science articles needing expert attention
Copyedit :
- Computing
Expand :
- Computer science
Infobox :
- Computer science articles without infoboxes
Maintain :
- Timeline of computing 2020–present
Photo :
- Find pictures for the biographies of computer scientists (see List of computer scientists)
- Computing articles needing images
Stubs :
- Computer science stubs
Unreferenced :
- WikiProject Computer science/Unreferenced BLPs
Project-related :
- Tag all relevant articles in Category:Computer science and sub-categories with {{WikiProject Computer science}}

As of 12 May 2013, this article is largely nonsense, written by persons who have no understanding of the issues. It could be safely deleted without loss to the wikipedia. It is so bad, reading it is currently a waste of time.

The title of the article is meaningful, however, so with some relevant content, it could be useful.

The "Distributed Deadlock" section is a verbatim lift from the wikipedia article entitled "Deadlock". The use of jargon is excessive, but the section is the only one in the article that has any well defined substance.

What the article should describe:

Multiprocessing algorithms for preventing irresolvable requests for shared resources that lead to the failure of a computation to proceed. This really has nothing to do with the halting problem. The banker's algorithm is one such algorithm, although it is neither especially good nor especially practical.

Recursive locks are perfectly valid tools, and so do not need to be "prevented", and in any case have nothing to do with the deadlock issue: like any lock, they merely ensure that competing processes do not corrupt one another's data.