The main method's logic is moved to a "main" RT thread that has the 8th RT priority.
main方法的逻辑被移到了一个具有第8RT优先级的“main”RT线程中。
Also, programs that monitor system state or provide system login should run at high RT priority so that the program is allowed to preempt the problematic threads.
另外，监控系统状态或提供系统登录的程序应该以高rt优先级运行，以便程序可以抢占问题线程。
It makes the compilation thread operate at a lower priority than RT tasks and is tuned to avoid generating code with severely nondeterministic performance effects.
使编译线程以低于RT任务的优先级操作，并且作出了调整以避免生成带有严重的不确定性性能影响的代码。
A dispatched thread with an RT priority is allowed to execute until it blocks, voluntarily relinquishes control by yielding, or is preempted by a thread with a higher RT priority.
具有RT优先级的调度线程可以一直执行直至阻塞，通过让步自愿放弃控制权，或被具有更高rt优先级的线程抢占。
To do this, we set the thread priority of the polling threads to 38 (the highest RT priority) and the priorities of the triage pool threads to 37.
为此，我们将轮询线程的线程优先级设置为38（最高的RT 优先级），将筛选池线程的优先级设置为 37。
Yielding only to a thread of the same priority means that Thread.yield is of questionable use in an RT application that USES more than one RT priority.
只让步给具有相同优先级的线程意味着在使用多个RT优先级的RT应用程序中使用Thread .yield可能会出现问题。
This priority is higher than the priority given to either of the two other RT threads that the main RT thread creates.
这个优先级比主RT线程创建的两个其他 RT线程的优先级都要高。
Standard Linux versions support a single default policy, whereas rt Linux versions also support the priority inheritance locking policy.
标准的Linux版本支持单个的默认策略，而RT Linux版本还支持优先级继承锁定策略。
RT Linux prevents priority inversion through a policy known as priority inheritance (also known as priority lending), illustrated in Figure 2's bottom diagram.
RTLinux通过使用名为优先级继承(也称作优先级借出(priority lending))的策略防止发生优先级反转，图2底部的图表做了解释。
JIT compilation can be used for softer RT scenarios where compilation can occur when no higher priority work needs to be done.
JIT编译可用于软rt场景，其中编译将在不需要执行高优先级任务时发生。
The first solution is to employ a JIT compiler, operating at a low non-RT priority, that has been modified to perform fewer aggressively speculative optimizations.
第一个解决方案是使用JIT编译器，在较低的非rt优先级上运行，它已被修改为很少执行主动的推测性优化。
To prevent this situation, the JVM forces the primordial thread to have a non-RT priority — that is, have a SCHED_OTHER policy.
为了防止这种情形，JVM强制原始线程拥有非rt优先级——即拥有sched_other策略。
Operation at a non-RT priority lets the operating system guarantee that the compiler will never interfere with the execution of a RT task.
非rt优先级的操作使操作系统保证编译器不会干扰RT任务的执行。
With the RTSJ, true priorities and a fixed-priority preemptive scheduler with priority-inheritance support is required for RT threads.
在RTSJ 规范中，RT线程需要真正的优先级，以及具有优先级继承支持的固定优先级抢占式调度程序。
Synchronization must be carefully managed within a RT system to prevent high-priority threads from waiting for lower-priority threads.
在RT系统中必须小心地管理同步，以防止高优先级线程等待低优先级线程的情况发生。
The alarm thread, being a high-priority RT thread, preempts any other lower-priority thread, and the GC thread also runs at an RT priority.
alarm线程是一个高优先级rt线程，它会抢占任何其他具有较低优先级的线程，而gc线程仍然以RT优先级运行。
应用推荐