rvu_npc_exa..._table_write(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… rvu_npc_exa..._table_write(9) β€” from the Kernel API Manual, bestie 🫢

Okay so welcome to the glow-up edition of the rvu_npc_exa..._table_write(9) page, straight out of the Kernel API Manual. Pull up a chair, grab a strawberry πŸ“, and let's get into it.


✨ NAME ✨

rvu_npc_exact_mem_table_write β€” literally just a wrapper for a register write, no cap. That's the whole vibe. πŸŽ€


🌸 SYNOPSIS 🌸

void rvu_npc_exact_mem_table_write (struct rvu *rvu , int blkaddr , u8
ways , u32 index , u64 mdata );

It returns void, so like… nothing comes back. It just does the thing. πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • rvu β€” the resource virtualization unit. The main character, honestly. πŸ‘‘
  • blkaddr β€” block address. Where the block lives, iykyk.
  • ways β€” the ways for the MEM table. Plural, because one way is never enough.
  • index β€” the index in MEM. Think of it as the seat number at the function.
  • mdata β€” the meta data to be written to the register. This is the payload, the moment, the content. ✨

πŸ’œ SEE ALSO πŸ’œ

The kernel file that started it all:

./drivers/net/ethernet/marvell/octeontx2/af/rvu_npc_hash.c

And the whole friend group, all showing up to the group chat in (9) form:

rvu_exact_prepare_mdata(9), rvu_exact_calculate_hash(9), rvu_npc_exact_alloc_mem_table_entry(9), rvu_npc_exact_free_id(9), rvu_npc_exact_alloc_id(9), rvu_npc_exact_alloc_cam_table_entry(9), rvu_exact_prepare_table_entry(9), rvu_exact_config_secret_key(9), rvu_exact_config_search_key(9), rvu_exact_config_result_ctrl(9), rvu_exact_config_table_mask(9), rvu_npc_exact_get_max_entries(9), rvu_npc_exact_has_match_table(9), __rvu_npc_exact_find_entry_by_seq_id(9), rvu_npc_exact_add_to_list(9), rvu_npc_exact_cam_table_write(9), rvu_npc_exact_dealloc_table_entry(9), rvu_npc_exact_alloc_table_entry(9), rvu_npc_exact_save_drop_rule_chan_and_mask(9), rvu_npc_exact_calc_drop_rule_chan_and_mask(9), rvu_npc_exact_drop_rule_to_pcifunc(9), rvu_npc_exact_get_drop_rule_info(9), __rvu_npc_exact_cmd_rules_cnt_update(9), rvu_npc_exact_del_table_entry_by_id(9), rvu_npc_exact_add_table_entry(9), rvu_npc_exact_update_table_entry(9), rvu_npc_exact_promisc_disable(9), rvu_npc_exact_promisc_enable(9), rvu_npc_exact_mac_addr_reset(9), rvu_npc_exact_mac_addr_update(9), rvu_npc_exact_mac_addr_add(9), rvu_npc_exact_mac_addr_del(9), rvu_npc_exact_mac_addr_set(9), rvu_npc_exact_can_disable_feature(9), rvu_npc_exact_disable_feature(9), rvu_npc_exact_reset(9), rvu_npc_exact_init(9)

No skipping, we listed every single one. Obsessed with our consistency. πŸ’€πŸ”₯


Ate. Every arg, every reference, all present and accounted for. That's the vibe check passed. βœ…

And that's the page, bestie! Big kiss from the source at ./drivers/net/ethernet/marvell..., dated October 2026, under the rvu_npc_exa..._table_write(9) name. Slay, go write some registers. πŸŒˆπŸ’–

πŸ“¦ where this page comes from