Searched refs:data_vios (Results 1 – 2 of 2) sorted by relevance
213 returned to a pool of data_vios for reuse.215 There is a fixed pool of 2048 data_vios. This number was chosen to bound376 that causes other data_vios to wait for the allocation process to388 updated, the data_vio proceeds down the tree. Any other data_vios411 claims that data_vios can have on physical blocks. The pbn_lock is434 the data_vios currently writing the same data. Active hash locks are472 agent and any other data_vios waiting on it will record this476 data_vios becomes the new agent and continues to step 8d as if no501 evict waiting data_vios when continuing to wait would cause525 physical address with as many other data_vios in the hash lock as[all …]
178 struct data_vio data_vios[]; member875 struct data_vio *data_vio = &pool->data_vios[i]; in make_data_vio_pool()1059 struct data_vio *data_vio = &pool->data_vios[i]; in dump_data_vio_pool()
Completed in 17 milliseconds