hns_dsaf_tbl_tcam_data_cfg(9)
π
hns_dsaf_tbl_tcam_data_cfg β a whole page from the Kernel API Manual, bestie β¨
Okay so picture this: you're deep in the kernel, you open up the Kernel API Manual, and this little icon pops out β hns_dsaf_tbl_tcam_data_cfg. That's the function we're talking about today. It's a void function, it's giving "quietly essential," and we're gonna get you two (2) arguments deep into it. Let's go π
β¨ NAME β¨
hns_dsaf_tbl_tcam_data_cfg β tbl. That's literally it, that's the whole name description. Short. Mysterious. Main character energy π
πΈ SYNOPSIS πΈ
void hns_dsaf_tbl_tcam_data_cfg (struct dsaf_device *dsaf_dev , struct
dsaf_tbl_tcam_data *ptbl_tcam_data );
So it returns nothing (void, no notes, no receipts, we love a function that doesn't overpromise π
) and it takes exactly two things. Keep reading, they're right below π«Ά
π¦ ARGUMENTS π¦
dsaf_devβ the dsa fabric id, fr fr. That's what the manual says and we are not adding to it. It's thestruct dsaf_device *you pass in.ptbl_tcam_dataβ addr. Yes, that's the entire description. Iconic brevity. It's yourstruct dsaf_tbl_tcam_data *and it's carrying the addr. Periodt π
π₯ SEE ALSO π₯
Okay bestie, buckle in, because this list is long and every single one of them is going in here. No skipping, no "etc.", no pretending we didn't see them π
First up, the file where the magic lives:
./drivers/net/ethernet/hisilicon/hns/hns_dsaf_main.c
Then the whole friend group:
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_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_uc_cfg_vague(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)
Yeah. Fifty-seven friends plus the source file. Ate. No crumbs. π
ngl bestie, this page is short on prose but stacked on cross-references β so if you're clicking through, the file above is your home base π
π§ sign-off π§
Source vibes come from ./drivers/net/ethernet/hisilic... (yes, the page literally truncates it like that, we respect the truncation π), dated October 2026, and the whole thing is filed under hns_dsaf_tbl_tcam_data_cfg(9). Slay, go config your tcam data πβ¨
π¦ 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