read_mod_write(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… read_mod_write(9) β€” like, the kernel API manual page, bestie πŸŽ€

Okay so this is read_mod_write, straight out of the 9 section of the manual β€” kernel API territory, iykyk. Buckle up, it's a short one but she's important. ✨


🌸 NAME 🌸

read_mod_write β€” the way we calculate the IRQ register index and set/clear the bits. That's literally the whole job description. No cap. πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

void read_mod_write (struct hfi1_devdata *dd , u16 src , u64 bits , bool
set );

That's it. That's the whole signature. She's void, she's got four args, she's doing her thing. πŸ”₯


✨ ARGUMENTS ✨

  • dd β€” a valid devdata, bestie. Valid. Don't be coming at her with your invalid devdata, she will not be having it πŸ™ˆ
  • src β€” the IRQ source, which is literally what we use to determine the register index from. Like, it's giving "lookup key" energy. πŸ”‘
  • bits β€” the bits that get set or get cleared. Whichever one you're on. Those bits. πŸ’–
  • set β€” true == set the bits, false == clear the bits. Iconic boolean behaviour, truly the main character of this function ngl ⭐

πŸ’œ SEE ALSO πŸ’œ

Okay so first up, the kernel file herself:

  • Kernel file ./drivers/infiniband/hw/hfi1/chip.c

And then the whole friend group, like the entire extended squad, all of them, no one left out 🫢:

Literally the whole chip.c friend group, go say hi to all of them πŸ’€


Lowkey a vibe check reminder: this page is read_mod_write(9) from the kernel API manual, and everything above is the whole page β€” no deleted sections, no cut lore, she's complete. 🧚

Mwah, that's a wrap bestie πŸ’‹ β€” this one comes to you from ./drivers/infiniband/hw/hfi1, dated October 2026, and it ate, periodt. 🌈

πŸ“¦ where this page comes from