src/share/vm/runtime/advancedThresholdPolicy.cpp

rev 5732 : [mq]: comments2

*** 304,314 ****
   * a. 0 -> 3 -> 4.
   *    The most common path. But note that even in this straightforward case
   *    profiling can start at level 0 and finish at level 3.
   *
   * b. 0 -> 2 -> 3 -> 4.
!  *    This case occures when the load on C2 is deemed too high. So, instead of transitioning
   *    into state 3 directly and over-profiling while a method is in the C2 queue we transition to
   *    level 2 and wait until the load on C2 decreases. This path is disabled for OSRs.
   *
   * c. 0 -> (3->2) -> 4.
   *    In this case we enqueue a method for compilation at level 3, but the C1 queue is long enough
--- 304,314 ----
   * a. 0 -> 3 -> 4.
   *    The most common path. But note that even in this straightforward case
   *    profiling can start at level 0 and finish at level 3.
   *
   * b. 0 -> 2 -> 3 -> 4.
!  *    This case occurs when the load on C2 is deemed too high. So, instead of transitioning
   *    into state 3 directly and over-profiling while a method is in the C2 queue we transition to
   *    level 2 and wait until the load on C2 decreases. This path is disabled for OSRs.
   *
   * c. 0 -> (3->2) -> 4.
   *    In this case we enqueue a method for compilation at level 3, but the C1 queue is long enough