That's the core of the work queue API.

这就是工作队列 API 的核心。

Work queue and servant region relationship

工作队列与服务区域的关系

To flush the kernel-global work queue, call flush_scheduled_work.

为了清理内核全局工作队列，可调用 flush_scheduled_work。

All work on a given work queue can be completed using a call to flush_workqueue.

指定工作队列中的所有任务能够通过调用 flush_workqueue 来完成。

Let's now continue with a simple example of the work queue API.

下面我们看一个工作队列 API 的简单例子。

Thus, if the Gearman daemon fails, it can recreate the work queue on restart.

这样一来，如果 Gearman 守护程序故障，它就可以在重启后重新创建这个工作队列。

The following example illustrates a few of the core work queue API functions.

下面的例子说明了几个核心的工作队列 API 函数。

The fork-join framework reduces contention for the work queue by using a technique known as work stealing.

fork-join框架通过一种称作工作窃取（workstealing） 的技术减少了工作队列的争用情况。

Executors are implemented with a single incoming work queue shared by all worker threads.

Executor是在单个传入的工作队列由多个工作线程共享的情况下实现的。

For the former, the Gearman work queue remains in memory but is backed by a relational database.

对于前者，Gearman 工作队列保存在内存并在一个关系型数据库内存有备份。