Home
last modified time | relevance | path

Searched refs:gcwq (Results 1 – 3 of 3) sorted by relevance

/linux-3.4.99/kernel/
Dworkqueue.c135 struct global_cwq *gcwq; /* I: the associated gcwq */ member
179 struct global_cwq *gcwq; /* I: the associated gcwq */ member
268 #define for_each_busy_worker(worker, i, pos, gcwq) \ argument
270 hlist_for_each_entry(worker, pos, &gcwq->busy_hash[i], hentry)
559 (data & WORK_STRUCT_WQ_DATA_MASK))->gcwq; in get_work_gcwq()
575 static bool __need_more_worker(struct global_cwq *gcwq) in __need_more_worker() argument
577 return !atomic_read(get_gcwq_nr_running(gcwq->cpu)) || in __need_more_worker()
578 gcwq->flags & GCWQ_HIGHPRI_PENDING; in __need_more_worker()
585 static bool need_more_worker(struct global_cwq *gcwq) in need_more_worker() argument
587 return !list_empty(&gcwq->worklist) && __need_more_worker(gcwq); in need_more_worker()
[all …]
/linux-3.4.99/Documentation/
Dworkqueue.txt94 The backend is called gcwq. There is one gcwq for each possible CPU
95 and one gcwq to serve work items queued on unbound workqueues.
105 When a work item is queued to a workqueue, the target gcwq is
107 and appended on the shared worklist of the gcwq. For example, unless
109 queued on the worklist of exactly that gcwq that is associated to the
118 Each gcwq bound to an actual CPU implements concurrency management by
119 hooking into the scheduler. The gcwq is notified whenever an active
125 CPU, the gcwq doesn't start execution of a new work, but, when the
136 the gcwq for the pseudo unbound CPU tries to start executing all work
179 gcwq which hosts workers which are not bound to any specific
[all …]
/linux-3.4.99/include/trace/events/
Dworkqueue.h57 __entry->cpu = cwq->gcwq->cpu;