[concurrency-interest] Java Deadlocks prevented
hans.boehm at hp.com
Mon Apr 16 12:38:00 EDT 2012
Important questions to consider when you write it up:
How does it compare to something like Gadara that uses whole program analysis and scheduling to avoid lock-based deadlocks? (Hopefully it doesn't need whole program analysis.) Other deadlock avoidance schemes?
Once you detect a potential deadlock, how do you recover? Or can you always schedule so that the possibility doesn't arise?
> -----Original Message-----
> From: concurrency-interest-bounces at cs.oswego.edu [mailto:concurrency-
> interest-bounces at cs.oswego.edu] On Behalf Of Andrew Haley
> Sent: Monday, April 16, 2012 4:34 AM
> To: concurrency-interest at cs.oswego.edu
> Subject: Re: [concurrency-interest] Java Deadlocks prevented
> On 04/16/2012 12:06 PM, Rohit Kumar wrote:
> > I have found a way of preventing deadlocks in java. The
> > methodology(which is code) completely prevents the deadlock from
> > occuring by detecting it in advance. This can be used across the
> > systems seamlessly.
> > Kindly let me know what I need to do next. I want this to be part of
> > next jdk release. I am writing this email as I have no idea what I
> > need to do next to bring it into limelight.
> Write it up, maybe present it to a conference, and wait for feedback.
> That's how it always works. If your idea really works, people will
> use it.
> Concurrency-interest mailing list
> Concurrency-interest at cs.oswego.edu
More information about the Concurrency-interest