Pls review 7091418: FX priority class from Solaris should be available to JVM
charlie.hunt at oracle.com
Mon Jan 23 12:46:22 PST 2012
On 01/23/12 01:26 PM, Paul Hohensee wrote:
> I've got one review (from a Reviewer), need another (doesn't have to
> be a Reviewer).
> On 1/20/12 12:13 PM, Paul Hohensee wrote:
>> Webrev here
>> This change defines a new Java pseudo-priority called
>> CriticalPriority, just
>> above MaxPriority. Compiler threads, the CMS background thread, and
>> Java threads can have the os equivalent of this priority. On
>> Solaris, this is
>> the FX/60 scheduling class/priority. On other platforms, it's the same
>> as MaxPriority's os priority.
>> There are 3 new command line switches, all gated by
>> Maps Java MAX_PRIORITY to critical priority.
>> All compiler threads run at critical priority.
>> The CMS background thread runs at critical priority.
>> On Solaris, one must in addition use -XX:+UseThreadPriorities to use
>> priorities at all. Otherwise, Hotspot just accepts whatever Solaris
>> Before this change, the Solaris implementation could only change
>> within the process scheduling class. It didn't change scheduling
>> classes on
>> a per-thread basis. I added that capability and used it for the
>> critical thread
>> work. I also fixed a bug where we were using thr_setprio() to save the
>> original native priority during thread creation and reading it back when
>> the thread started via thr_getprio(). Since thr_setprio() can change
>> user-supplied priority, this resulted in an unintended (lower) priority
>> being used.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 5166 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mail.openjdk.java.net/pipermail/hotspot-runtime-dev/attachments/20120123/ead52844/smime.p7s
More information about the hotspot-runtime-dev