That's the core of the work queue API.
这就是工作队列api的核心。
Work queue and servant region relationship
工作队列与服务区域的关系
Listing 1 shows an example of a simple pooled work queue.
清单1显示了简单的合用工作队列的示例。
Let's now continue with a simple example of the work queue API.
下面我们看一个工作队列api的简单例子。
WUQue is the total number of requests taken from the work queue.
WUQue是从工作队列接收的请求总数。
A new request comes in and stays in the new service class work queue.
新的请求传入并滞留在新的服务分类工作队列中。
The Activities act like a work queue, where work is assigned and completed.
这些活动像一个工作队列，工作在这里被分配和完成。
The work queue mechanism is inherited from the WLM queuing manager service.
工作队列机制是从wlm队列管理器服务继承而来的。
The following class is a model of a common concurrent utility: a work queue.
下面的类是一种常见的并行实用程序模型：任务队列。
The following example illustrates a few of the core work queue API functions.
下面的例子说明了几个核心的工作队列api函数。
Thus, if the Gearman daemon fails, it can recreate the work queue on restart.
这样一来，如果Gearman守护程序故障，它就可以在重启后重新创建这个工作队列。
All work on a given work queue can be completed using a call to flush_workqueue.
指定工作队列中的所有任务能够通过调用flush _ workqueue来完成。
Before the request is processed by the servant region, it's put inside the WLM work queue.
在服务区域处理请求之前，请求被放在WLM工作队列中。
The work to be communicated through the work queue is defined by the work_struct structure.
通过工作队列与之通信的任务可以由结构体work_struct来定义。
Upon successful creation of the work queue, you create two work items (allocated via kmalloc).
成功生成工作队列之后，创建两个任务项目（通过 kmalloc 来分配）。
For the former, the Gearman work queue remains in memory but is backed by a relational database.
对于前者，Gearman工作队列保存在内存并在一个关系型数据库内存有备份。
You can use a global kernel-global work queue, with four functions that address this work queue.
可以使用全局的内核全局工作队列，利用4个函数来为工作队列定位。
The work queue API provides three functions to initialize work (from an allocated buffer); see Listing 6.
工作队列API提供三个函数来初始化任务（通过一个事先分配的缓存）；参见清单6。
The fork-join framework reduces contention for the work queue by using a technique known as work stealing.
fork - join框架通过一种称作工作窃取(work stealing)的技术减少了工作队列的争用情况。
Finally, Query also includes the option to constrain a search to a particular container (folder or work queue).
最后，Query还包含将搜索限制在特定容器(文件夹或工作队列)的选项。
In the panel shown in Figure 11, there are two servant regions bound to the same service class work queue, CBDEF.
在如图11所示的面板中，有两个服务区域与同一个服务分类工作队列CBDEF绑定。
WebSphere Application Server for z/OS combines a work queue mechanism with the thread pool to serve the client requests.
WebSphereApplicationServerfor z/OS 将工作队列机制与线程池组合起来为客户端请求提供服务。
As the work_struct indicates the handler function to use, you can use the work queue to queue work for a variety of handlers.
由于work_struct中指出了要采用的处理程序函数，因此可以利用工作队列来为不同的处理程序进行任务排队。
The optimum size of a thread pool depends on the number of processors available and the nature of the tasks on the work queue.
线程池的最佳大小取决于可用处理器的数目以及工作队列中的任务的性质。
Listing 10 is your init_module function, which begins with creation of the work queue using the create_workqueue API function.
清单10是init _ module函数，该函数从使用create _ workqueueapi函数生成工作队列开始。
These functions (shown in Listing 8) mimic those from Listing 7, except that you don't need to define the work queue structure.
这些函数(见清单8)模拟清单7，只是不需要定义工作队列结构体。
The column WUQue reports only the number of requests taken from the service class work queue that are bound to the server region.
WUQue列仅报告从服务分类工作队列接收并绑定到该服务区域的请求数量。
The administration work queue lets you see the list of administration actions queued up on a broker that are waiting to be actioned
管理工作队列使您可以查看在一个等待行动的代理上排队等候的管理活动的列表
You can find the implementation of the work queue API in ./kernel/workqueue.c, with API definitions in ./include/linux/workqueue.h.
在./kernel/workqueue.c 中能够找到工作队列API的实现方法， API 在 ./include/linux/workqueue.h 中定义。
You can find the implementation of the work queue API in ./kernel/workqueue.c, with API definitions in ./include/linux/workqueue.h.
在./kernel/workqueue.c 中能够找到工作队列API的实现方法， API 在 ./include/linux/workqueue.h 中定义。
应用推荐