Do you use kernel threads to run I/O requests?
你使用内核线程来运行I/O请求吗？
Designing kernel threads and test applications.
设计内核线程和测试应用程序。
You will need two kernel threads in this approach.
在这种方法中需要两个内核线程。
The scheduler manipulates a limited number of Kernel threads.
该调度程序处理有限数量的内核线程。
To achieve this you need application threads and kernel threads.
要实现这种功能，我们需要几个应用程序线程和内核线程。
You will need two kernel threads for the implementation of this strategy.
要实现这种策略，我们需要两个内核线程。
These kernel threads should be destroyed in the close of the device driver.
这些内核线程应该在设备驱动程序的close函数中进行销毁。
If this number is climbing, then you should consider adding more NFS kernel threads.
如果这个数字比较大，就应该考虑增加NFS内核线程。
Almost all interrupt handlers are converted to kernel threads that run in process context.
几乎所有的中断处理程序都被转换为运行在进程中的内核线程。
The bindprocessor command binds or unbinds the kernel threads of a process to a processor.
bindprocessor命令可以将进程中的内核线程绑定到一个处理器，或取消这种绑定。
It reports statistics about kernel threads, virtual memory, disks, traps, and CPU activity.
它将报告关于内核线程、虚拟内存、磁盘、自陷和CPU活动的统计信息。
r—The average number of runnable kernel threads over the timing interval you have specified.
r——在您指定的时间间隔内，可运行内核线程的平均数量。
R — The average number of runnable kernel threads over whatever sampling interval you have chosen.
r——在所选择的任意采样间隔期间的平均可运行内核线程数。
Once kernel threads of the process are bound, they'll always be scheduled to run on the selected processor.
在对进程的内核线程进行绑定之后，它们将会被调度运行于指定的处理器。
With the exception of NFS kernel threads, you can set and then ignore the parameters discussed in this article.
除了NFS内核线程之外，可以设置本文中讨论的参数，然后就不用理会它们了。
B — the average number of kernel threads that are in the virtual memory waiting queue over your sampling interval.
b——采样期间在虚拟内存中等待队列的平均内核线程数。
B-the average number of kernel threads that are in the virtual memory waiting queue over your timing interval.
b——在您指定的时间间隔内，位于虚拟内存等待队列中的内核线程的平均数量。
On the server side, it is important to make sure there are enough NFS kernel threads available to handle all your clients.
在服务器端，一定要确保有足够的NFS内核线程来处理所有客户机。
With specific kernel threads, it designs multiple channels for the network subsystem, which supports the concurrent schedule.
为网络子系统设计多个处理通道，支持网络并发调度，这由多个针对不同应用的内核线程实现。
With the libpthreads implementation, user threads sit on top of virtual processors, which are themselves on top of kernel threads.
在libpthread实现中，用户线程位于虚拟处理器之上，而虚拟处理器本身又位于内核线程之上。
Codezero's scheduler includes kernel preemption for both guest threads and microkernel threads (in addition to time slices for preemption).
Codezero的调度器包含针对来宾线程和微核线程的内核优先(以及用于优先的时间片)。
The process itself actually owns the kernel threads and each process can have one or more kernel threads (for example, multi-threaded applications).
实际上，进程本身也拥有内核线程，每个进程可具有一个或多个内核线程(例如多线程应用程序)。
vmstat reports back information about kernel threads, CPU activity, virtual memory, paging, blocked I/O disks, and related information (see Listing 3).
vmstat 可以报告许多信息，包括内核线程、CPU活动、虚拟内存、分页、阻塞的I/O磁盘、以及相关信息（请参见清单3）。
AIX V7.1 adds scalability enhancements to the base kernel, drivers and libraries to scale up to 1024-way partitions, which are partitions with 256 processor cores and four hardware threads per core.
AIXV7.1在基本内核、驱动程序和库中增强了可伸缩性，能够扩展到最多1024路的分区，分区有256个处理器核，每核有四个硬件线程。
Special signals like SIGSTOP would have to be handled by the kernel and for all threads.
SIGSTOP等专用信号必须由内核来为所有线程处理。
In the kernel, these are called threads and represent an individual virtualization of the processor (thread code, data, stack, and CPU registers).
在内核中，这些进程称为线程，代表了单独的处理器虚拟化(线程代码、数据、堆栈和CPU寄存器)。
This enables a 1:1 threading model without limitations on the number of threads being created (since a new kernel thread is created for every user thread).
这样就可以实现一个不受创建的线程数限制的1:1线程模型（因为每一个新的内核线程都是为一个用户线程而创建）。
The Linux kernel provides a lightweight process framework for creating threads; the actual thread implementation is in the user space.
Linux内核提供了一个轻量级进程框架来创建线程；实际的线程在用户空间中实现。
Threading operations will enjoy an increase in speed; the 2.6 kernel can now handle an arbitrary number of threads and up to 2 billion PIDs (on IA32).
线程操作可以提高速度；2.6内核现在可以处理任意数目的线程，PID最大可以到20亿(IA32上)。
The Linux kernel performs thread scheduling based on static controls, such as thread priority levels, and on certain dynamic conditions of the threads executing in the system.
Linux核心可以根据静态控制(如线程优先级级别)和系统中执行的线程的某些动态条件下来执行线程调度。
应用推荐