工作队列接口是在2.5的开发过程中引入的，用于取代任务队列接口(用于调度内核任务)。
Workqueue interface is introduced in 2.5 development to replace the task queue interface (used to schedule kernel tasks).
该调度类类似于一个模块链，协助内核调度程序工作。
The scheduling classes are like a chain of modules assisting the core scheduler.
在对进程的内核线程进行绑定之后，它们将会被调度运行于指定的处理器。
Once kernel threads of the process are bound, they'll always be scheduled to run on the selected processor.
内核实现了一种新型的调度算法，不管有多少个线程在竞争CPU，这种算法都可以在固定时间内进行操作。
The kernel implements a novel scheduling algorithm that operates in constant time, regardless of the number of threads vying for the CPU.
内核调度程序使用这种方法实现由调度模块管理的进程的负载平衡。
The core scheduler USES this method to load-balance processes managed by the scheduling module.
另一方面，对于CPU，内核要从wlm调度程序读取关于CPU使用量的输入，以便做出调度决策。
On the other hand, in the case of CPU, the input from the WLM scheduler about CPU usage is read by the kernel to make scheduling decisions.
内核使用收集的CPU 使用量数据，可以根据优先级、当前 CPU 使用量和 CPU 限制调度或撤消运行进程。
The CPU usage thus gathered is used by the kernel, which may schedule or de-schedule a process based on its priority, current CPU usage, and CPU limits.
但是O(1)调度器在内核中很笨拙。
调度代码在内核中实现。
然后资源内核可以合并这些请求，使用任务定义的约束定义一个调度，从而提供确定的访问（如果无法提供确定性则返回错误）。
The resource kernel can then merge the requests to define a schedule to provide guaranteed access using the task-defined constraints (or return an error if they cannot be guaranteed).
SSI解决方案会修改内核的几乎所有部分：进程管理、文件系统、内存 管理、调度器，等等。通过不加修改地运行内核进程，模拟器简化了部署工作。
SSI solutions modify almost every area of kernel: process management, filesystem, memory management, scheduler, etc. Emulators simplify the deployment by letting the kernel processes run unchanged.
CFS另一个有趣的地方是组调度概念(在2.6.24内核中引入)。
Another interesting aspect of CFS is the concept of group scheduling (introduced with the 2.6.24 kernel).
LinSched使用Linux内核代码自身(通过仿真平台的包装器)，而不是构建新的框架(通过该框架可以在用户空间中完成调度)。
Rather than build a new framework through which scheduling could be accomplished in user space, LinSched USES the Linux kernel code itself (with wrappers for platform emulation).
task_new：内核调度程序为调度模块提供了管理新任务启动的机会。
Task_new: the core scheduler gives the scheduling module an opportunity to manage new task startup.
这种改变来自ConKolivas的内核补丁，其中包括他的RotatingstaircaseDeadlineScheduler (RSDL)，这包含了他在staircase调度器方面的早期工作。
That change came in the way of a kernel patch from Con Kolivas, with his Rotating staircase Deadline scheduler (RSDL), which included his earlier work on the staircase scheduler.
要了解有关调度的更多信息，包括那些在Linux内核中实现的算法，请在Wikipedia中查看调度(计算)页面。
To learn more about scheduling, including those algorithms implemented in the Linux kernel, check out the scheduling (computing) page at Wikipedia.
进程被调度的次数(或者说是内核调度子例程为那个进程释放CPU的次数)。
Number of times that the process was dispatched (or how many times the kernel dispatch subroutine relinquished the CPU to that process).
Linux内核中的 NPTL实现需要重写 Linux 内核调度程序（scheduler）、扩展标准的glibc以及更新GNUbinutils以支持该实现。
NPTL implementation in the Linux kernel required the Linux kernel scheduler to be rewritten, the standard glibc to be extended, and updates to the GNU binutils to support it.
由于标准Linux内核就是一个系统管理程序，因此它会从对标准内核的修改中获益良多(内存支持、调度程序等)。
Because the standard Linux kernel is the hypervisor, it benefits from the changes to the standard kernel (memory support, scheduler, and so on).
内核代码中子例程是idled （当CPU空闲时运行的进程）和schedule（内核调度器）。
The subroutines that ran in the kernel code are idled (the process that is run when the CPU is idle) and schedule (the kernel scheduler).
对这些Linux组件进行优化(例如2.6版本内核中的新o(1)调度程序)都可以让系统管理程序(主机操作系统)和Linux客户操作系统同时受益。
Optimizations to these Linux components (such as the new o (1) scheduler in the 2.6 kernel) benefit both the hypervisor (the host operating system) and the Linux guest operating systems.
该调度程序处理有限数量的内核线程。
The scheduler manipulates a limited number of Kernel threads.
内核中称为调度程序的部分将工作换进换出，从而让所有工作都获得一轮执行。
The part of the kernel called the scheduler swaps jobs in and out so that they all get a turn.
每个卫星内核都是由调度器、内存管理器、命名空间管理器以及协调与其他内核通信的代码所组成的。
Each satellite kernel is composed of a scheduler, a memory manager, a namespace manager, and code to coordinate communication between other kernels.
这意味着一旦在用户空间中验证了调度器，将此调度器迁移到内核以供使用会非常简单。
This means that once a scheduler is validated in user space, it's quite simple then to migrate this scheduler into the kernel for use.
在2.6版本的内核之前，当很多任务都处于活动状态时，调度器有很明显的限制。
Before the 2.6 kernel, the scheduler had a significant limitation when many tasks were active.
WLM调度程序读取并报告内核数据。
The WLM scheduler just reads the kernel data and reports it.
当ISR对这个tasklet/bootomhalf 进行调度时，内核就会在这个断点处停止。
The kernel will stop at this point when the ISR schedules the tasklet/bottom half.
为实现上述目标，微核创建一个只包含基本服务(如内存管理和调度)的内核并将其他功能推到内核之外。
Microkernels do this by creating a kernel (which includes the basic services like memory management and scheduling) and pushing all other functionality outside the kernel.
为实现上述目标，微核创建一个只包含基本服务(如内存管理和调度)的内核并将其他功能推到内核之外。
Microkernels do this by creating a kernel (which includes the basic services like memory management and scheduling) and pushing all other functionality outside the kernel.
应用推荐