清单4：进程上下文命令。
然而，轮询线程是在一个普通进程上下文中运行的。
However, the polling thread will run in a normal process context.
即使你改变调试器进程上下文，它仍然是属于内核，没有过程。
Even if you change the process context in debugger, it is still attached to kernel, not process.
清单4中有用的进程上下文命令是使用前面定义的数据转储函数来构建的。
The useful process context commands in Listing 4 are built by using the previously defined data dumping functions.
只有在重新调度是在两个进程间进行的时候，进程上下文才被转换。
The process context only needs switching if a reschedule is between threads in different processes.
最后，当您调试正在运行的进程时，获得进程上下文的总体视图通常是必要的。
Finally, when you're debugging a running process, it's often necessary to get an overall view of the process context.
进程上下文包含通用寄存器、浮点寄存器、特殊用途的寄存器和其他有关重启线程所需的信息。
The process context includes the general purpose registers, floating point registers, the special purpose registers, and other information necessary to restart a thread when it is dispatched.
你需要在进程上下文之外访问内存的原因也许是一些驱动在SYSTEM进程中创建了线程。
The reason you may need to access memory outside the current process context is that some drivers create threads in the SYSTEM process.
注意：必须在返回前完成任何必须在用户进程上下文中完成的工作，因为随后是不能访问用户进程上下文的。
Note that any work that must be done within the user process's context must be done before returning; you will not have access to that context later.
这个状态不但仅包含了处理器寄存器(进程上下文)而且还包含了线程可访问的地址空间(进程上下文)。
This state includes not only the processor registers (the thread context) but also the address space accessible to the thread (the process context).
当asp.netISAPI工作在IIS6进程模式下，其行为不同，只是在w3wp . exe工作进程上下文中加载clr。
When the ASP.NET ISAPI works under the IIS 6 process model, it behaves differently and just loads the CLR in the context of the w3wp.exe worker process.
从asp.net的角度来看，IIS6最大的变化是一切与请求相关的东西发生在aspnet _ isapi控制下，并且工作在w3wp . exe进程上下文中。
From the ASP.NET perspective, the big change with IIS 6 is that everything about a request takes place under the control of aspnet_isapi and in the context of the w3wp.exe.
它提供了同一进程中的应用程序或安全上下文之间安全通信的方法。
It provides a way to safely communicate between applications or security contexts in the same process.
由于任意工作量的一个线程或进程的上下文切换涉及到的开销较大，小粒度级的系统往往效率低下且遭遇低性能问题。
Due to the overhead involved in context switching to a thread or process for any amount of work, systems with small-scope granularity are often inefficient and suffer from low performance.
当它执行另一个程序时，进程的安全上下文可以改变。
A process 'security context can be changed when it executes another program.
除了执行其指令之外，进程有时还会管理打开文件、处理器上下文、地址空间以及与程序相关的数据等。
Apart from executing its instructions, a process might be engaged in managing open files, processor context, address space, and data related to the program, among other things.
因为更改发生在本地(在进程中)，所以应用服务器本身必须为执行过程更改安全上下文。
Since the change happens locally (in-process) the application server itself has to change the security context for the execution.
有了微线程，我们就可能在目前中等性能的PC 机上运行数以万计的并行进程，还可以每秒钟几十万次地在上下文之间切换。
With microthreads, it is possible to run tens of thousands of parallel processes on a moderately capable modern PC, and to switch between contexts hundreds of thousands of times every second.
这个示例中的数据展示了机器CPU的0和6.7%之间所用的计算进程，不过非常基本并且脱离了上下文。
Though very basic and out of context, the data in this example shows that the calc process used between 0 and 6.7% of the machine's CPU.
为键不安全的内核进程自动地固定上下文堆栈。
The context stack is automatically pinned for key-unsafe kernel processes.
MQI还允许应用程序操作队列上下文、发布或订阅主题、以及查询进程和名称列表。
The MQI can also allow a program to manipulate context for queues, specify alternate userids, publish or subscribe to topics, and inquire on processes and namelists.
现代操作系统通常在进程调度方面表现得很出色，从而最大程度减少了上下文切换。
Modern operating systems generally do an excellent job of process scheduling, which minimizes context switching.
mkdir系统调用用来创建这个上下文，用户进程然后可以打开这个目录中相关的文件。
The mkdir system call creates the context, and the user process can subsequently open the associated files inside that directory.
在调用其start()方法之前，还可以调整进程所执行的上下文。
Prior to calling its start() method, you can adjust the context for the process to execute in.
但是，登录进程将使用Linux用户名来为安全上下文选择SELinux用户。
The login process, however, uses the Linux username to choose an SELinux user for your security context.
SELinux用户不是Linux用户名，而是附加到进程和文件的SELinux上下文(由id -Z返回)的一部分。
The SELinux user is not the Linux username, but rather the first piece of the SELinux context (returned by id -z) attached to a process and file.
但是与web服务进程的分离，使得仅工作在一个内存上下文的应用程序本质上变慢。
But just working in a memory context distinct from the Web server process makes the application intrinsically slower.
指定角色mgr_r中的进程可以切换到角色cashier_r中的有效上下文。
Specifying that a process in role mgr_r may switch to a valid context in role cashier_r. But there is no line.
另外管理端还能查看所有的上下文(所有的执行进程)。
A spectator context also exists for administration (to view all executing processes).
另外管理端还能查看所有的上下文(所有的执行进程)。
A spectator context also exists for administration (to view all executing processes).
应用推荐