vdo_configure_slab(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– vdo_configure_slab(9) β€” Kernel API Manual πŸ’–

✨ NAME ✨

vdo_configure_slab β€” measure and initialize the configuration to use for each slab. That's the whole assignment, bestie: slab config, handled. πŸ’…

🌸 SYNOPSIS 🌸

int vdo_configure_slab (block_count_t slab_size , block_count_t
       slab_journal_blocks , struct slab_config *slab_config );

🫢 ARGUMENTS 🫢

  • slab_size β€” the number of blocks per slab. 🧱
  • slab_journal_blocks β€” the number of blocks for the slab journal. πŸ““
  • slab_config β€” the slab configuration to initialize. πŸ› οΈ

πŸŽ€ RETURN πŸŽ€

Returns VDO_SUCCESS or an error code. That's the vibe check: success, or the error code situation. 😌

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./drivers/md/dm-vdo/encodings.c and the whole cross-ref crew: validate_version(9), vdo_validate_header(9), decode_volume_geometry(9), vdo_encode_volume_geometry(9), vdo_parse_geometry_block(9), vdo_compute_new_forest_pages(9), encode_recovery_journal_state_7_0(9), decode_recovery_journal_state_7_0(9), vdo_get_journal_operation_name(9), encode_slab_depot_state_2_0(9), decode_slab_depot_state_2_0(9), vdo_configure_slab_depot(9), vdo_decode_slab_journal_entry(9), allocate_partition(9), make_partition(9), vdo_initialize_layout(9), vdo_uninitialize_layout(9), vdo_get_partition(9), vdo_get_known_partition(9), pack_vdo_config(9), pack_vdo_component(9), unpack_vdo_config(9), unpack_vdo_component_41_0(9), decode_vdo_component(9), vdo_validate_config(9), vdo_destroy_component_states(9), decode_components(9), vdo_decode_component_states(9), vdo_validate_component_states(9), vdo_encode_component_states(9), vdo_encode_super_block(9), vdo_decode_super_block(9), vdo_initialize_component_states(9), vdo_compute_index_blocks(9), vdo_initialize_volume_geometry(9).


xoxo, your kernel bestie πŸ’– β€” source/version ./drivers/md/dm-vdo, date October 2026, page vdo_configure_slab(9). mwah πŸ’‹

πŸ“¦ where this page comes from