STRUCT MPT3SAS_TARGET(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct MPT3SAS_TARGET(9)

okay bestie, welcome to the Kernel API Manual β€” yes we're literally reading kernel headers for fun now, and honestly? iconic behavior. this page is all about struct MPT3SAS_TARGET, which is the starget private hostdata. that's it, that's the vibe. πŸŽ€


✨ NAME ✨

struct MPT3SAS_TARGET β€” starget private hostdata. lowkey the little private clubhouse where a scsi_target keeps its hostdata. no cap. πŸ¦‹


✨ SYNOPSIS ✨

struct MPT3SAS_TARGET {
    struct scsi_target *starget;
    u64 sas_address;
    struct _raid_device *raid_device;
    u16 handle;
    int num_luns;
    u32 flags;
    u8 deleted;
    u8 tm_busy;
    struct hba_port *port;
    struct _sas_device *sas_dev;
    struct _pcie_device *pcie_dev;
 };

like, look at her. every field exactly where it belongs, not me being obsessed with a struct definition at 2am πŸ™ˆ


✨ Members ✨

🌸 the fields, one by one

  • starget β€” the starget object. the whole reason we're here tbh πŸ’–
  • sas_address β€” the target's SAS address. it's giving "government name but for a device" 🫢
  • raid_device β€” a raid_device pointer, used to access volume data. pointer to the volume data, periodt ✨
  • handle β€” the device handle. short, sweet, load-bearing πŸ”₯
  • num_luns β€” number luns. yes, that's the original wording, and yes, we're keeping it exactly as-is, character for character, because them's the rules πŸ‘‘
  • flags β€” MPT_TARGET_FLAGS_XXX flags. all the little vibes, in bit form πŸ’…
  • deleted β€” target flagged for deletion 😭 (iykyk, this one's a mood)
  • tm_busy β€” target is busy with TM request. busy busy, do not perceive her ⭐
  • port β€” hba port entry containing the target's port number info. like a tiny ID card for her port 🌈
  • sas_dev β€” the sas_device associated with this target πŸ¦‹
  • pcie_dev β€” the pcie device associated with this target 🧚
ngl bestie, if you're poking at these fields directly you better know what you're doing, because this is kernel-land and the vibes there are unforgiving πŸ’€

✨ SEE ALSO ✨

kernel file ./drivers/scsi/mpt3sas/mpt3sas_base.h β€” that's where this struct lives, go say hi to her πŸ‘‘

and the whole friend group, fr fr:

  • struct MPT3SAS_DEVICE(9)
  • struct _internal_cmd(9)
  • struct _sas_device(9)
  • pcie_device_get(9)
  • pcie_device_free(9)
  • pcie_device_put(9)
  • struct _boot_device(9)
  • struct _sas_port(9)
  • struct _sas_phy(9)
  • struct _sas_node(9)
  • struct _enclosure_node(9)
  • enum reset_type(9)
  • struct pcie_sg_list(9)
  • struct chain_tracker(9)
  • struct scsiio_tracker(9)
  • struct request_tracker(9)
  • struct _tr_list(9)
  • struct _sc_list(9)
  • struct _event_ack_list(9)
  • struct adapter_reply_queue(9)
  • struct io_uring_poll_queue(9)
  • struct virtual_phy(9)
  • struct hba_port(9)
  • struct htb_rel_query(9)
  • struct MPT3SAS_ADAPTER(9)

that's the whole page, bestie. every field, every cross-reference, nothing dropped. go forth and read the source πŸ’œ

and finally, the cute sign-off you asked for: this lil page comes from ./drivers/scsi/mpt3sas, dated October 2026, and it's filed under struct MPT3SAS_TARGET(9) β€” see you in the man page index, mwah πŸŽ€βœ¨πŸ’–

πŸ“¦ where this page comes from