Lines Matching refs:nr_running

211 	int			nr_running;
948  * Note that, because unbound workers never contribute to nr_running, this
954 	return !list_empty(&pool->worklist) && !pool->nr_running;
966 	return !list_empty(&pool->worklist) && (pool->nr_running <= 1);
986  * worker_set_flags - set worker flags and adjust nr_running accordingly
990  * Set @flags in @worker->flags and adjust nr_running accordingly.
998 	/* If transitioning into NOT_RUNNING, adjust nr_running. */
1001 		pool->nr_running--;
1008  * worker_clr_flags - clear worker flags and adjust nr_running accordingly
1012  * Clear @flags in @worker->flags and adjust nr_running accordingly.
1024 	 * If transitioning out of NOT_RUNNING, increment nr_running.  Note
1030 			pool->nr_running++;
1072 	/* Sanity check nr_running. */
1073 	WARN_ON_ONCE(pool->nr_workers == pool->nr_idle && pool->nr_running);
1459 	 * and the nr_running increment below, we may ruin the nr_running reset
1460 	 * and leave with an unexpected pool->nr_running == 1 on the newly unbound
1465 		worker->pool->nr_running++;
1508 	 * want to decrement nr_running after the worker is unbound
1509 	 * and nr_running has been reset.
1516 	pool->nr_running--;
1555 	 * @pool->nr_running until it wakes up. As wq_worker_sleeping() also
1556 	 * decrements ->nr_running, setting CPU_INTENSIVE here can lead to
3342 	 * since nr_running would always be >= 1 at this point. This is used to
6836 		 * The handling of nr_running in sched callbacks are disabled
6837 		 * now.  Zap nr_running.  After this, nr_running stays zero and
6843 		pool->nr_running = 0;
6895 		 * worker_clr_flags() or adjust nr_running.  Atomically