On 08/20/13 17:50, Libin wrote: > No functional changes. This patch fixes the post gcwq comments in > Documentation/workqueue.txt. > > Signed-off-by: Libin <huawei.li...@huawei.com> > --- > Documentation/workqueue.txt | 72 > ++++++++++++++++++++++----------------------- > 1 file changed, 36 insertions(+), 36 deletions(-) > > diff --git a/Documentation/workqueue.txt b/Documentation/workqueue.txt > index a6ab4b6..5e65b1c 100644 > --- a/Documentation/workqueue.txt > +++ b/Documentation/workqueue.txt > @@ -85,16 +85,16 @@ workqueue. > Special purpose threads, called worker threads, execute the functions > off of the queue, one after the other. If no work is queued, the > worker threads become idle. These worker threads are managed in so > -called thread-pools. > +called worker-pools. > > The cmwq design differentiates between the user-facing workqueues that > subsystems and drivers queue work items on and the backend mechanism > -which manages thread-pools and processes the queued work items. > +which manages worker-pools and processes the queued work items. > > -The backend is called gcwq. There is one gcwq for each possible CPU > -and one gcwq to serve work items queued on unbound workqueues. Each > -gcwq has two thread-pools - one for normal work items and the other > -for high priority ones. > +There are two worker-pools, one for normal work items and the other > +for high priority ones, for each possible CPU and some extra worker-pools > +to serve work items queued on unbound workqueues - the number of these > +baking pools is dynamic.
backing ? > > Subsystems and drivers can create and queue work items through special > workqueue API functions as they see fit. They can influence some -- ~Randy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
