hns_dsaf_tcam_uc_cfg_vague(9)
π hns_dsaf_tcam_uc_cfg_vague(9) β Kernel API Manual, but make it make sense
okay so bestie, we're in the Kernel API Manual today and the function we're stanning is hns_dsaf_tcam_uc_cfg_vague. Yes, that's the whole name. Yes, you have to type it. No, there is no shorter version. iykyk. π
β¨ NAME β¨
hns_dsaf_tcam_uc_cfg_vague β INT
yep. that's it. that's the description. one word. the manpage said INT and honestly? iconic minimalism. we respect it. π«Ά
πΈ SYNOPSIS πΈ
void hns_dsaf_tcam_uc_cfg_vague (struct dsaf_device *dsaf_dev , u32
address , struct dsaf_tbl_tcam_data *tcam_data , struct
dsaf_tbl_tcam_data *tcam_mask , struct dsaf_tbl_tcam_ucast_cfg *tcam_uc
);
it returns void, so likeβ¦ don't go looking for a return value, she's not giving you one π
π¦ ARGUMENTS π¦
five params, five besties, let's meet them:
dsaf_devβ dsa fabric device struct pointer. this is the main character, the device we're messing with β¨addressβ the address. yes. the address. lowkey the most mysterious member of the group chat πtcam_dataβ the datatcam_maskβ the masktcam_ucβ the unicast data
three of them are literally just "the data", "the mask", "the unicast data" and honestly the original author ate and left no crumbs. we're keeping it exactly like that fr fr π
π SEE ALSO π
first up, the source file where all this lives:
- Kernel file
./drivers/net/ethernet/hisilicon/hns/hns_dsaf_main.c
and now, the full friend group β every single one of these, no skips, no cap π
hns_dsaf_sbm_link_sram_init_en(9)hns_dsaf_reg_cnt_clr_ce(9)hns_dsaf_ppe_qid_cfg(9)hns_dsaf_sw_port_type_cfg(9)hns_dsaf_stp_port_type_cfg(9)hns_dsaf_sbm_cfg(9)hns_dsaf_sbm_cfg_mib_en(9)hns_dsaf_sbm_bp_wl_cfg(9)hns_dsaf_voq_bp_all_thrd_cfg(9)hns_dsaf_tbl_tcam_data_cfg(9)hns_dsaf_tbl_tcam_mcast_cfg(9)hns_dsaf_tbl_tcam_ucast_cfg(9)hns_dsaf_tbl_line_cfg(9)hns_dsaf_tbl_tcam_mcast_pul(9)hns_dsaf_tbl_line_pul(9)hns_dsaf_tbl_tcam_data_mcast_pul(9)hns_dsaf_tbl_tcam_data_ucast_pul(9)hns_dsaf_tbl_stat_en(9)hns_dsaf_rocee_bp_en(9)hns_dsaf_single_line_tbl_cfg(9)hns_dsaf_tcam_uc_cfg(9)hns_dsaf_tcam_mc_cfg(9)hns_dsaf_tcam_mc_cfg_vague(9)hns_dsaf_tcam_mc_invld(9)hns_dsaf_tcam_uc_get(9)hns_dsaf_tcam_mc_get(9)hns_dsaf_tbl_line_init(9)hns_dsaf_tbl_tcam_init(9)hns_dsaf_pfc_en_cfg(9)hns_dsaf_comm_init(9)hns_dsaf_inode_init(9)hns_dsaf_sbm_init(9)hns_dsaf_tbl_init(9)hns_dsaf_voq_init(9)hns_dsaf_init_hw(9)hns_dsaf_remove_hw(9)hns_dsaf_init(9)hns_dsaf_free(9)hns_dsaf_find_soft_mac_entry(9)hns_dsaf_find_empty_mac_entry(9)hns_dsaf_find_empty_mac_entry_reverse(9)hns_dsaf_set_mac_key(9)hns_dsaf_set_mac_uc_entry(9)hns_dsaf_add_mac_mc_port(9)hns_dsaf_del_mac_entry(9)hns_dsaf_del_mac_mc_port(9)hns_dsaf_free_dev(9)hns_dsaf_pfc_unit_cnt(9)hns_dsaf_port_work_rate_cfg(9)hns_dsaf_fix_mac_mode(9)hns_dsaf_get_regs(9)hns_dsaf_get_stats(9)hns_dsaf_get_sset_count(9)hns_dsaf_get_strings(9)hns_dsaf_get_regs_count(9)hns_dsaf_probe(9)hns_dsaf_remove(9)
like, that's the whole hns_dsaf extended universe right there. collect them all π
ngl bestie, this page is short and the vibe is "the kernel devs were busy" β but every detail is here, exactly as written, and that's what matters π
and that's the tea π β this page came from ./drivers/net/ethernet/hisilic..., dated October 2026, and it's still wearing its hns_dsaf_tcam_uc_cfg_vague(9) name tag at the door. slay, honestly. πβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms