Lines Matching full:handlers

39  * Each cpu will have HP_PER_CPU "handlers" set up, each of which incorporates
41  * organisation of FQIDs is such that the HP_PER_CPU*NUM_CPUS handlers will
44  * is to allow enough handlers/FQs to truly test the significance of caching -
65  *    handlers and link-list them (but do no other handler setup).
162 	/* root node for the per-cpu list of handlers */
163 	struct list_head handlers;  member
168 	 * handlers together, this is used as per-cpu iterator state
186 /* handlers are allocated out of this, so they're properly aligned. */
328 	INIT_LIST_HEAD(&hp_cpu->handlers);  in create_per_cpu_handlers()
339 		list_add_tail(&handler->node, &hp_cpu->handlers);  in create_per_cpu_handlers()
352 	list_for_each_safe(loop, tmp, &hp_cpu->handlers) {  in destroy_per_cpu_handlers()
455 						&hp_cpu->handlers,  in init_phase2()
479 	handler = list_first_entry(&hp_cpu->handlers, struct hp_handler, node);  in init_phase2()
498 						&hp_cpu->handlers,  in init_phase3()
587 	pr_info("Creating %d handlers per cpu...\n", HP_PER_CPU);  in qman_test_stash()
593 	pr_info("Number of cpus: %d, total of %d handlers\n",  in qman_test_stash()