Home
last modified time | relevance | path

Searched refs:data_vios (Results 1 – 2 of 2) sorted by relevance

/linux/Documentation/admin-guide/device-mapper/
H A Dvdo-design.rst213 returned to a pool of data_vios for reuse.
215 There is a fixed pool of 2048 data_vios. This number was chosen to bound
333 application bio. If there are no data_vios available, the incoming bio
376 that causes other data_vios to wait for the allocation process to
388 updated, the data_vio proceeds down the tree. Any other data_vios
411 claims that data_vios can have on physical blocks. The pbn_lock is
434 the data_vios currently writing the same data. Active hash locks are
472 agent and any other data_vios waiting on it will record this
474 to record their new mapping. If there are more data_vios in the hash
476 data_vios becomes the new agent and continues to step 8d as if no
[all …]
/linux/drivers/md/dm-vdo/
H A Ddata-vio.c179 struct data_vio data_vios[]; member
872 struct data_vio *data_vio = &pool->data_vios[i]; in make_data_vio_pool()
1062 struct data_vio *data_vio = &pool->data_vios[i]; in dump_data_vio_pool()