> The test result of caleb's testcase is,
>
> =A0 =A0./ruby projects/thrprio/thrprio.rb
> =A0 =A0315662770 209679 0.9986723818385312 true

Oops, please use following test instead caleb's one. because my
experimental patch haven't implement the way to chnage another thread
priority yet.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
c1 =3D c2 =3D 0
go=3Dnil
t2 =3D Thread.new {
  t2.priority =3D -2;
  loop { c2 +=3D 1 }
}
t1 =3D Thread.new {
  t1.priority =3D -1;
  loop { c1 +=3D 1 }
}
go=3Dtrue
sleep 5
t1.kill
t2.kill
puts "#{c1} #{c2} #{(c1-c2).to_f/(c1+c2)} #{c1.to_f/c2} #{c1 > c2}"
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Note: if we use /proc/sys/kernel/sched_compat_yield=3D1, we can get better =
result.

% taskset -c 1  ./ruby projects/thrprio/thrprio2.rb
16989126 12636726 0.14691223057483713 1.3444246555634742 true