lpfc_adjust_high_watermark(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… lpfc_adjust_high_watermark(9) β€” Kernel API Manual ✨

okay so bestie, welcome to the Kernel API Manual entry for lpfc_adjust_high_watermark. it's a whole vibe. short function, big responsibilities. let's get into it 🫢


πŸŽ€ NAME πŸŽ€

lpfc_adjust_high_watermark β€” Adjust high watermark

like, it adjusts the high watermark. that's the whole thing. iconic brevity honestly πŸ’…


✨ SYNOPSIS ✨

void lpfc_adjust_high_watermark (struct lpfc_hba *phba , u32 hwqid );

returns nothing, takes two things. no notes. 🌸


πŸ¦‹ ARGUMENTS πŸ¦‹

  • phba β€” pointer to lpfc hba data structure. like, the whole HBA's whole personality, passed by reference bestie 🫢
  • hwqid β€” belong to which HWQ. that's the hardware queue we're talking about, in case there was any doubt ✨

πŸ’– DESCRIPTION πŸ’–

so this routine sets the high watermark as the number of outstanding XRIs β€” but (and this is the important part, don't skip it) it makes sure the new value lands between xri_limit/2 and xri_limit. no cap. it will not let the number escape that range. it's giving responsible. it's giving boundaries. we love to see it πŸ‘‘


🌈 SEE ALSO 🌈

Kernel file ./drivers/scsi/lpfc/lpfc_sli.c β€” and honestly? the whole friend group showed up. every single one of these is invited to the function party πŸŽ‰

that's the whole list, bestie β€” no skips, no "etc." i would never 🫢

anyway that's the page!! written from the ./drivers/scsi/lpfc source tree, dated October 2026, and it's the lpfc_adjust_high_watermark(9) page πŸ’œ thanks for reading, ily, go set a watermark that's actually between xri_limit/2 and xri_limit ok bye πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from