mpi3mr_cfg_s..._io_unit_pg1(9)

📦 version 7.3.1, in nixpkgs unstable

💖 mpi3mr_cfg_set_sas_io_unit_pg1 💖

okay so bestie, welcome to the Kernel API Manual page for mpi3mr_cfg_set_sas_io_unit_pg1 — yes that's a mouthful, yes we're gonna get through it together, and yes it's giving "I memorized the whole driver source" main character energy 🎀

✨ NAME ✨

mpi3mr_cfg_set_sas_io_unit_pg1 — literally just Write SASIOUnit page1. that's the whole vibe. it writes the page. slay 🫶

🌸 SYNOPSIS 🌸

int mpi3mr_cfg_set_sas_io_unit_pg1 (struct mpi3mr_ioc *mrioc , struct
mpi3_sas_io_unit_page1 *sas_io_unit_pg1 , u16 pg_sz );

like, no cap, that's the whole signature. three args, one int coming back at you 💅

🦋 ARGUMENTS 🦋

  • mrioc — the adapter instance reference 💖 this is your controller's whole little identity card.
  • sas_io_unit_pg1 — pointer to the SAS IO Unit page 1 that we're about to write ✨ it's the actual page data, bestie.
  • pg_sz — size of the memory allocated to the page pointer 📏 (so the function knows how much room it's working with, iykyk).

💜 DESCRIPTION 💜

okay so this is the handler for config page write for the SAS IO Unit page1. that's the whole job description and honestly? iconic.

what it does: this routine checks ioc_status to decide whether the page read is a success or not 👀 — yes, "read", that's what the page says, we're not gonna argue with it, we're just reporting it fr fr.

and then — big one — this will modify both current and persistent page 😭 so it's not just a vibe, it's an actual durable write. both. current and persistent. the way that it commits... periodt 💅

🔥 RETURN 🔥

  • 0 on success 🎉
  • non-zero on failure 💀

that's it. that's the return. binary mood.

🌈 SEE ALSO 🌈

Kernel file ./drivers/scsi/mpi3mr/mpi3mr_fw.c — and honestly, the entire friend group is here, so let's shout them all out 🫶 no skipping, we list every single one:

like I said — the whole group chat 💀 and the file we're living in is ./drivers/scsi/mpi3mr 🧚

💡 tiny heads-up bestie: this page lists the SAS IO Unit page1 write handler, and the description says it checks ioc_status to decide whether the page read is a success, and that it modifies both the current and the persistent page. that's straight from the page, no additions from me, okay? 😌

so yeah — that's the whole manpage, every flag, every argument, every cross-reference, nothing dropped, nothing invented 🌟 stay hydrated, read your kernel source, and remember: 0 on success, non-zero on failure, and you are always the main character 💖

written for the Kernel API Manual, sourced from ./drivers/scsi/mpi3mr, dated October 2026, and filed under mpi3mr_cfg_s..._io_unit_pg1(9) — mwah, bye bestie! 👑💅🎀

📦 where this page comes from