STRUCT SCU_SGL_ELEMENT_PAIR(9)

💅 struct scu_sgl_element_pair(9)

okay so we're in the Kernel API Manual bestie, and today's main character is this little struct 🎀

---

✨ NAME ✨

struct scu_sgl_element_pair — this structure is the SCU hardware definition of a pair of SGL elements. fr fr, that's the whole vibe: the SCU hardware always works on SGL pairs. No solo acts, no single-element situations — pairs only, periodt. 💅

They're referred to in the DS specification as SGL A and SGL B (yes, the original doc spells it "refered" — iconic typo, we're preserving the lore 🙈). And each SGL pair is followed by the address of the next pair, so they chain along like a little group chat 🫶

---

🌸 SYNOPSIS 🌸

struct scu_sgl_element_pair {
    struct scu_sgl_element A;
    struct scu_sgl_element B;
    u32 next_pair_upper;
    u32 next_pair_lower;
 };

Like, look at it. Two elements, A and B, sitting right next to each other, then the upper and lower halves of the next-pair address. So clean. So structured. Lowkey obsessed. ✨

---

🦋 Members 🦋

ngl the original page keeps this heading and then… says nothing under it 😭 the member breakdown is simply not giving. Empty. A void. But we're keeping the section because the order matters, bestie — we don't skip parts in this house 👑

---

🔥 SEE ALSO 🔥

• Kernel file ./drivers/scsi/isci/scu_task_context.h enum
• scu_ssp_task_type(9)
• enum scu_sata_task_type(9)
• struct ssp_task_context(9)
• struct stp_task_context(9)
• struct smp_task_context(9)
• struct primitive_task_context(9)
• struct scu_sgl_element(9)
• struct transport_snapshot(9)
• struct scu_task_context(9)

go read those too, iykyk 💖

---

heads up bestie: this whole page is about hardware-defined layout, so treat the field order and types as gospel — no cap, no "let me just reorder these", just vibes-preserving accuracy 🔥

---

and that's the whole page!! 🎀 source/version is ./drivers/scsi/isci and it's dated October 2026, so like, future-dated slay ⭐💜 mwah, go read your task contexts 🌈