Received: from PACIFIC-CARRIER-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA02150; Fri, 15 Mar 96 10:35:59 EST Received: from liquor.cabi.net by MIT.EDU with SMTP id AA07084; Fri, 15 Mar 96 10:35:10 EST Received: by liquor.cabi.net (8.7.3/8.7.3) id KAA10140; Fri, 15 Mar 1996 10:30:49 -0500 Resent-Date: Fri, 15 Mar 1996 10:30:49 -0500 Date: Fri, 15 Mar 1996 07:23:38 -0800 (PST) From: craig horman To: Lincoln Stein Cc: java-linux@java.blackdown.org, mieg@kaa.crbm.cnrs-mop.fr Subject: Re: Thread.yield() doesn't In-Reply-To: <199603151437.PAA06152@pico.crbm.cnrs-mop.fr> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-Id: <"jt6R1.0.wS2.jpOIn"@liquor> Resent-From: java-linux@java.blackdown.org X-Mailing-List: archive/latest/1400 X-Loop: java-linux@java.blackdown.org Precedence: list Resent-Sender: java-linux-request@java.blackdown.org I've no idea if this will help, but as a general suggestion: there is an excellent discussion of `Concurrent Programming in Java,' written by Doug Lea, at http://g.oswego.edu/dl/pats/aopintro.html. I'm not implying you haven't found a linux-specific problem, but Lea's paper is comprehensive enough that you might find an alternative solution that will work. I recommend this paper to anyone interested in java threads. It's truly an impressive piece of work. Regards, Craig On Fri, 15 Mar 1996, Lincoln Stein wrote: > [...] > The problem is that time-slicing doesn't seem to be implemented on the > Linux platform. The first thread grabs the CPU and holds onto it > until its inner read-and-parse loop is done. Very annoying. > [...]