ice_update_pkg(9)
π NAME π
ice_update_pkg β okay so bestie, this is the Kernel API Manual entry for the ice driver's package updater, and I need you to know that the original manpage literally leaves the description after the dash blank. Empty. Nothing. A whole void. So the name is all we're getting and honestly? We respect the mystery. π«Ά
β¨ SYNOPSIS β¨
int ice_update_pkg (struct ice_hw *hw , struct ice_buf *bufs , u32 count
);
π ARGUMENTS π
Three of them, no cap, and here's exactly what each one is:
hwβ pointer to the hardware structure π that's it, that's the whole jobbufsβ pointer to an array of buffers β¨ yes, an array, plural energycountβ the number of buffers in the array πΈ so it knows how many besties are in the group chat
πΈ DESCRIPTION πΈ
So what does it do? Two things, and they're both in the original and I refuse to add a third:
- It obtains the change lock π
- It updates the package π¦
That's the whole arc. Lock first, then update β the order is giving main character energy and it is NOT up for discussion. Lowkey iconic that a function can be this brief and still be trusted with a lock. π
π¦ SEE ALSO π¦
Kernel file ./drivers/net/ethernet/intel/ice/ice_ddp.c β that's where the real lore lives, go read it iykyk π
And now the extended universe, bestie. Sixty-nine entries. I counted. Not me counting. I did count. π Every single one, in order, exactly as written, no merges, no skips:
ice_verify_pkg(9)ice_free_seg(9)ice_chk_pkg_version(9)ice_pkg_val_buf(9)ice_find_buf_table(9)ice_pkg_enum_buf(9)ice_pkg_advance_sect(9)ice_pkg_enum_section(9)ice_pkg_enum_entry(9)ice_sw_fv_handler(9)ice_get_prof_index_max(9)ice_get_ddp_pkg_state(9)ice_init_pkg_regs(9)ice_marker_ptype_tcam_handler(9)ice_add_dvm_hint(9)ice_add_tunnel_hint(9)ice_label_enum_handler(9)ice_enum_labels(9)ice_boost_tcam_handler(9)ice_find_boost_entry(9)ice_is_init_pkg_successful(9)ice_pkg_buf_alloc(9)ice_get_sw_prof_type(9)ice_get_sw_fv_bitmap(9)ice_get_sw_fv_list(9)ice_init_prof_result_bm(9)ice_pkg_buf_free(9)ice_pkg_buf_reserve_section(9)ice_pkg_buf_alloc_section(9)ice_pkg_buf_alloc_single_section(9)ice_pkg_buf_get_active_sections(9)ice_pkg_buf(9)ice_acquire_global_cfg_lock(9)ice_release_global_cfg_lock(9)ice_aq_download_pkg(9)ice_is_buffer_metadata(9)struct ice_ddp_send_ctx(9)ice_ddp_send_hunk(9)ice_dwnld_cfg_bufs_no_lock(9)ice_get_pkg_seg_by_idx(9)ice_is_signing_seg_at_idx(9)ice_is_signing_seg_type_at_idx(9)ice_download_pkg_sig_seg(9)ice_download_pkg_config_seg(9)ice_dwnld_sign_and_cfg_segs(9)ice_match_signing_seg(9)ice_post_dwnld_pkg_actions(9)ice_download_pkg_with_sig_seg(9)ice_dwnld_cfg_bufs(9)ice_download_pkg_without_sig_seg(9)ice_download_pkg(9)ice_aq_get_pkg_info_list(9)ice_aq_update_pkg(9)ice_aq_upload_section(9)ice_update_pkg_no_lock(9)ice_find_seg_in_pkg(9)ice_has_signing_seg(9)ice_get_pkg_segment_id(9)ice_get_pkg_sign_type(9)ice_get_signing_req(9)ice_init_pkg_info(9)ice_get_pkg_info(9)ice_chk_pkg_compat(9)ice_init_pkg_hints(9)ice_fill_hw_ptype(9)ice_init_pkg(9)ice_copy_and_init_pkg(9)ice_get_set_tx_topo(9)ice_cfg_tx_topo(9)
not me clocking that ice_update_pkg_no_lock(9) is sitting right there in the list while this page says it obtains the change lock π two different functions bestie, read the names, they're literally different functions, do not come for me π«Ά
okay that's the whole page!! no notes, it's short and it's perfect and we love a concise king π π β
this came out of ./drivers/net/ethernet/intel/ice (source/version, and yes that's where you'll find the code) and it's dated October 2026 β future-dated manpage, she's ahead of her time π
β¨ π πΈ π¦
π¦ 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