sci_stp_requ..._data_buffer(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… sci_stp_requ..._data_buffer(9) β€” Kernel API Manual, but make it make sense

okay so bestie, welcome to the kernel API manual, where the function names are lowkey longer than my attention span 🫢 this one lives in the kernel docs and it's a little helper that does exactly one thing, and honestly? it slays at that one thing.


✨ NAME ✨

sci_stp_request_pio_data_in_copy_data_buffer β€”

(fr fr, that's the whole name section. the manpage just drops the name and a lil trailing dash and leaves. mysterious main character energy, we respect it πŸ’…)


🌸 SYNOPSIS 🌸

enum sci_status sci_stp_request_pio_data_in_copy_data_buffer (struct
isci_stp_request *stp_req , u8 *data_buf , u32 len );

like, look at her. enum sci_status going in, enum sci_status coming out. iconic πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • stp_req β€” the request that's used for the SGL processing. it's a struct isci_stp_request *, and it's the one holding the SGL we're about to poke at. she's the main character here.
  • data_buf β€” the buffer of data to be copied. it's a u8 *, so yes, bytes. bytes in a row. we love that for us πŸ¦‹
  • len β€” the length of the data transfer. a u32. it tells us how much of the buffer we're actually moving, so pls don't make it lie πŸ™ˆ

πŸ’– DESCRIPTION πŸ’–

so here's the vibe: you take the data from the buffer, and for the length specified you copy it over to the data region that the IO request's SGL points at. that's it. that's the whole function. copy β†’ length β†’ into the SGL's specified data region. no cap.

and the return type is enum sci_status, bestie. enum sci_status. don't forget it πŸ’€


πŸ¦‹ SEE ALSO πŸ¦‹

like a whole friend group of functions, and they all get their own (9) section refs. obsessed 🌈


and that's the page!! sign-off time: this one comes from ./drivers/scsi/isci and it's dated October 2026 β€” so yeah, future-dated kernel lore. mwah, take care of her πŸ’œβœ¨πŸŽ€

πŸ“¦ where this page comes from