Date: Mon, 2 Feb 1998 17:49:15 +1100 (EST) From: John Birrell <jb@cimlogic.com.au> To: nate@mt.sri.com (Nate Williams) Cc: jb@cimlogic.com.au, nate@mt.sri.com, SSANKARA.IN.oracle.com.ofcmail@in.oracle.com, freebsd-java@FreeBSD.ORG Subject: Re: TimeSlicing in JVM Message-ID: <199802020649.RAA00688@cimlogic.com.au> In-Reply-To: <199802020636.XAA26813@mt.sri.com> from Nate Williams at "Feb 1, 98 11:36:21 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Nate Williams wrote: > I also remember thinking seriously about this problem after reading a > Java threads book, and they brought up another point that I can't recall > right now that was also one of those 'syscall' types of problems. If I > remember or find it I'll send something to the list. It might be a scheduler issue. Like the one where a lower priority thread locks a resource that a higher priority thread needs, but the lower priority thread can't get enough CPU time to finish using the resource. libc_r deals with this by using an incremental priority that is reset when a thread gets to run, but is incremented the longer it is ready to run but prevented from running. Eventually the lower priority thread has a higher effective priority and gets to see its name in lights. Regards, -- John Birrell - jb@cimlogic.com.au; jb@netbsd.org; jb@freebsd.org CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199802020649.RAA00688>