Lines Matching refs:concurrency

39 Although MT wq wasted a lot of resource, the level of concurrency
47 The tension between the provided level of concurrency and resource
51 MT wq don't provide much better concurrency, users which require
52 higher level of concurrency, like async or fscache, had to implement
61   flexible level of concurrency on demand without wasting a lot of
64 * Automatically regulate worker pool and level of concurrency so that
97 concurrent execution context, there's no need to worry about concurrency.
106 things like CPU locality, concurrency limits, priority and more.  To
117 For any thread pool implementation, managing the concurrency level
119 tries to keep the concurrency at a minimal but sufficient level.
123 Each worker-pool bound to an actual CPU implements concurrency
128 maintaining just enough concurrency to prevent work processing from
144 regulating concurrency level is on the users.  There is also a flag to
145 mark a bound wq to ignore the concurrency management.  Please refer to
196   context provider without concurrency management.  The unbound
201   * Wide fluctuation in the concurrency level requirement is
226   implements concurrency management among its workers.
230   concurrency level.  In other words, runnable CPU intensive
237   concurrency level, start of their executions is still
238   regulated by the concurrency management and runnable
355   recommended.  In most use cases, concurrency level usually stays
396   workqueues without concurrency management.