Lines Matching refs:t
51 MT wq don't provide much better concurrency, users which require
65 the API users don't need to worry about such details.
122 workers on the CPU, the worker-pool doesn't start execution of a new
124 schedules a new worker so that the CPU doesn't sit idle while there
128 Keeping idle workers around doesn't cost other than the memory space
199 Note that normal and highpri worker-pools don't interact with
211 Although CPU intensive work items don't contribute to the
339 which are not involved in memory reclaim and don't need to be
340 flushed as a part of a group of work items, and don't require any
533 reduced to four, there now isn't enough work to saturate the whole system
587 kernel wouldn't be able to do the right thing and maintain
746 1. The work function hasn't been changed.
748 3. The work item hasn't been reinitiated.
754 doesn't break these conditions, so it's safe to do. Otherwise, caution is