1. 03 10月, 2013 1 次提交
  2. 10 6月, 2013 1 次提交
  3. 31 5月, 2013 1 次提交
  4. 27 5月, 2013 1 次提交
  5. 23 5月, 2013 1 次提交
  6. 21 5月, 2013 1 次提交
  7. 17 5月, 2013 1 次提交
  8. 16 5月, 2013 1 次提交
    • T
      8007763: Refactoring: split up compute_generation_free_space() into two... · d8e75982
      tamao 提交于
      8007763: Refactoring: split up compute_generation_free_space() into two functions for class PSAdaptiveSizePolicy
      Summary: split up compute_generation_free_space() into two functions: compute_eden_space_size() + compute_old_gen_free_space(), each of which (if needed) can be reused without executing an overhead of the other.
      Reviewed-by: jmasa, tschatzl
      Contributed-by: Ntamao <tao.mao@oracle.com>
      d8e75982
  9. 13 5月, 2013 1 次提交
  10. 26 4月, 2013 1 次提交
  11. 25 4月, 2013 1 次提交
  12. 10 4月, 2013 1 次提交
  13. 13 2月, 2013 1 次提交
  14. 23 4月, 2013 1 次提交
  15. 03 1月, 2013 1 次提交
  16. 27 11月, 2012 1 次提交
  17. 16 10月, 2012 1 次提交
  18. 25 9月, 2012 1 次提交
  19. 21 9月, 2012 1 次提交
  20. 02 9月, 2012 1 次提交
  21. 29 6月, 2012 1 次提交
    • Z
      6995781: Native Memory Tracking (Phase 1) · bdfb3cf5
      zgu 提交于
      7151532: DCmd for hotspot native memory tracking
      Summary: Implementation of native memory tracking phase 1, which tracks VM native memory usage, and related DCmd
      Reviewed-by: acorn, coleenp, fparain
      bdfb3cf5
  22. 15 5月, 2012 1 次提交
  23. 17 2月, 2012 1 次提交
  24. 01 2月, 2012 1 次提交
  25. 20 12月, 2011 1 次提交
    • J
      7117303: VM uses non-monotonic time source and complains that it is non-monotonic · 412f955f
      johnc 提交于
      Summary: Replaces calls to os::javaTimeMillis(), which does not (and cannot) guarantee monotonicity, in GC code to an equivalent expression that uses os::javaTimeNanos(). os::javaTimeNanos is guaranteed monotonically non-decreasing if the underlying platform provides a monotonic time source. Changes in OS files are to make use of the newly defined constants in globalDefinitions.hpp.
      Reviewed-by: dholmes, ysr
      412f955f
  26. 23 11月, 2011 1 次提交
  27. 23 9月, 2011 1 次提交
    • J
      6484982: G1: process references during evacuation pauses · 9c3adbcc
      johnc 提交于
      Summary: G1 now uses two reference processors - one is used by concurrent marking and the other is used by STW GCs (both full and incremental evacuation pauses). In an evacuation pause, the reference processor is embedded into the closures used to scan objects. Doing so causes causes reference objects to be 'discovered' by the reference processor. At the end of the evacuation pause, these discovered reference objects are processed - preserving (and copying) referent objects (and their reachable graphs) as appropriate.
      Reviewed-by: ysr, jwilhelm, brutisso, stefank, tonyp
      9c3adbcc
  28. 01 9月, 2011 1 次提交
  29. 10 8月, 2011 1 次提交
  30. 13 5月, 2011 1 次提交
  31. 08 4月, 2011 1 次提交
  32. 18 3月, 2011 1 次提交
  33. 28 1月, 2011 1 次提交
  34. 20 1月, 2011 1 次提交
  35. 24 11月, 2010 1 次提交
  36. 29 9月, 2010 1 次提交
  37. 21 9月, 2010 1 次提交
  38. 02 7月, 2010 1 次提交
  39. 28 5月, 2010 2 次提交