[Sablevm-developer] Implementing Deadlock Exceptions for SableVM
Brought to you by:
egagnon
From: Fancong Z. <fz...@cs...> - 2004-04-20 14:58:40
|
Hi, I just read your Ph.D. thesis. I like your extension of thin locks. I am now looking into the SableVM system and I hope SableVM has the following features: 1) Being able to run large real-life sever programs. E.g., Tomcat. 2) Supporting true parallelism. This requires kernel-level preemptive thread scheduling and SMP support --- I noticed a note about flaws in SMP, possible to improve the SMP support? 3) Accomodating JIT compilers seamlessly. I have some ideas to have a JIT generate recovery code, and I expect to see the JIT compilers to be incorporated to (the public version of) SableVM. Any comments/information on the three issues I list above? -- Fancong Zeng Department of Computer Science Rutgers University Piscataway, NJ, 08854 (732)445-6994 http://www.cs.rutgers.edu/~fzeng On Sun, 18 Apr 2004, Etienne Gagnon wrote: > Fancong Zeng wrote: > > I see a motivation to incorporate my work of "Deadlock Resolution via > > Exceptions for Dependable Java Applications" into SableVM. Anyone > > interested in co-working with me in implementing deadlock exceptions for > > SableVM? > > That would be pretty neat. I don't know, but both Greg P. and Chris P. > have touched the code related to locking, a little, and I have written > the code. I can't promise much availability, but I can usually answer > questions. SableVM's source code is not really cryptic (that's what I > hope, at least;-), and you can find information about the locking > algorithm in my Ph.D. thesis and the related papers by Bacon and by > Onodera. > > Would you be interested in getting a sandbox in the subversion repository > to do your work? [If yes, we'll have to clear up the legal aspects privately; > e.g. Are you or is Rutgers U. the copyright holder, and a few little > similar details.] > > Etienne > > -- > Etienne M. Gagnon, Ph.D. http://www.info.uqam.ca/~egagnon/ > SableVM: http://www.sablevm.org/ > SableCC: http://www.sablecc.org/ > |