> "Joseph" == Joseph Shraibman <[EMAIL PROTECTED]> writes:
Joseph> Juergen Kreileder wrote:
>> Please note that it is perfectly legal with respect to the JLS
>> to implement Thread.yield() as nop in JVMs based LinuxThreads.
>> Actually it is not only legal, it's desirable to i
Joseph Shraibman wrote:
> > Please note that it is perfectly legal with respect to the JLS to
> > implement Thread.yield() as nop in JVMs based LinuxThreads. Actually
> > it is not only legal, it's desirable to implement it as nop on JVMs
> > that employ preemptive scheduling policies (especiall
Juergen Kreileder wrote:
>
>
> Please note that it is perfectly legal with respect to the JLS to
> implement Thread.yield() as nop in JVMs based LinuxThreads. Actually
> it is not only legal, it's desirable to implement it as nop on JVMs
> that employ preemptive scheduling policies (especially
On Sun, 11 Feb 2001, Dimitris Vyzovitis wrote:
> > I'm not sure what you want to show with test_fairness. You have three
> > threads which all count up to the same number. Then finally you print
> > out the three counters which always will be the same. There's nothing
> > in this code testin
On 10 Feb 2001, Juergen Kreileder wrote:
> > "Dimitris" == Dimitris Vyzovitis <[EMAIL PROTECTED]> writes:
>
> Dimitris> On 9 Feb 2001, Juergen Kreileder wrote:
> >> BTW, it's "Thread.yield()". "Thread.currentThread().yield()"
> >> has exactly the same meaning but as Thread.yield
> "Dimitris" == Dimitris Vyzovitis <[EMAIL PROTECTED]> writes:
Dimitris> On 9 Feb 2001, Juergen Kreileder wrote:
>> BTW, it's "Thread.yield()". "Thread.currentThread().yield()"
>> has exactly the same meaning but as Thread.yield() is a class
>> method you should call it direc
On 9 Feb 2001, Juergen Kreileder wrote:
> BTW, it's "Thread.yield()". "Thread.currentThread().yield()" has
> exactly the same meaning but as Thread.yield() is a class method you
> should call it directly on the class.
> "Thread.currentThread().yield()" makes it look like yield() would be
> an in
> "Dimitris" == Dimitris Vyzovitis <[EMAIL PROTECTED]> writes:
Dimitris> On Thu, 8 Feb 2001, Joseph Shraibman wrote:
>> Is it just me or does Thread.yield() not work anymore with the
>> 2.4.0 kernel?
Dimitris> Interesting: blackdown jdk seems to indeed behave
Dimitris> in
On Thu, 8 Feb 2001, Joseph Shraibman wrote:
> Is it just me or does Thread.yield() not work anymore with the 2.4.0
> kernel?
Interesting: blackdown jdk seems to indeed behave incorrectly.
Sample execution of the test program I posted previously (I am on an smp
box with two processors, so the ca
