您要查找的是不是：
- process context switching 进程关联转换
- Gets the amount of physical memory mapped to the process context. 获取映射到进程上下文的物理内存量。
- The process context only needs switching if a reschedule is between threads in different processes. 只有在重新调度是在两个进程间进行的时候，进程上下文才被切换。
- The connection concentrator is associated with context switching of agents. 连接集中器与代理的上下文切换相关联。
- The CPU simply becomes overburdened by context switching between threads. 由于要在线程间进行上下文切换,因此CPU简直变成了超载。
- TSS holds hardware context information for each CPU which helps to take effect in context switching. TSS中保存了每个CPU的硬件上下文信息,它有助于有效地切换上下文。
- This is most likely due to the cost of context switching between so many threads. 这最有可能是由于在这么多的线程间切换上下文的开销而导致的。
- Containing the number of bytes of physical memory mapped to the process context. 包含映射到进程上下文的物理内存字节数的。
- This is true if there is no context switching or if the impersonation is at the server level. 没有上下文切换或在服务器级进行模拟时,将出现这种情况。
- Note that context switching on the front-end server does not grow significantly as processor usage increases. 请注意,当处理器的使用增加时,前端服务器的上下文切换不会显著增长。
- Rather, all protothreads run on the same stack and context switching is done by stack rewinding. 而且，所有的实例运行在同样的堆栈和内容切换通过堆栈反转完成。
- The business process context is strictly speaking multi-threaded, but in practice concurrency is sufficiently rare that this fact may be disregarded most of the time. 业务流程上下文严格的讲是多线程的，但是实际应用中，并发的情况非常少，大部分情况下都可以忽略。
- The following figure shows how context switching begins to level off on a two-processor front-end server as processor usage increases. 下图显示了双处理器前端服务器的上下文切换是如何随着处理器使用的增加而渐趋平稳的。
- As an alternative, the page table itself may occupy a different virtual-memory page for each process so that the page table becomes a part of the process context. 另外，各个进程的分页表本身可能也占有一个不同的虚拟存储页，分页表也变成了进程上下文的一部分。
- The topics in this section provide information to help you understand and implement context switching in modules and sessions. 本节中的主题提供信息来帮助您了解和实现在模块和会话中切换上下文。
- Number of scheduler context switches that this task has completed. 此任务完成的计划程序上下文切换数。
- The duration of the context switch is limited to the scope of the query being executed. 时,上下文切换的持续时间限制为执行查询的范围。
- If SESSION_USER is called after a context switch, SESSION_USER will return the user name of the impersonated context. 如果在切换上下文之后调用SESSION_USER,SESSION_USER将返回模拟上下文的用户名。
- When context switches are made on a thread, the next user-supplied code module stepped into may not relate to the code that was in the process of being debugged. 如果线程的上下文发生了转换,进入并单步执行的下一个由用户提供的代码模块可能与正在调试的代码无关。
- Specifies that the context switch cannot be reverted back to the previous context. 指定上下文切换不能恢复到以前的上下文。
