sci_req_tx_bytes(9)
β¨ sci_req_tx_bytes β¨
okay so bestie, welcome to the Kernel API Manual entry for sci_req_tx_bytes(9) β yes the (9) means it's a kernel thing, we love a section-nine moment π
π NAME π
sci_req_tx_bytes β literally tells you how many bytes got transferred when the reply underruns the request π«Ά
πΈ SYNOPSIS πΈ
u32 sci_req_tx_bytes (struct isci_request *ireq );
that's it, that's the whole signature β short and iconic, no notes π
π¦ ARGUMENTS π¦
ireqβ the request that was terminated early π like it got cut off mid-sentence, and this is the struct for it
π SEE ALSO π
bestie go read these, iykyk:
- Kernel file
./drivers/scsi/isci/request.c scu_ssp_task_request_construct_task_context(9)scu_sata_request_construct_task_context(9)sci_stp_request_pio_data_in_copy_data_buffer(9)sci_stp_request_pio_data_in_copy_data(9)isci_request_process_response_iu(9)isci_request_set_open_reject_status(9)isci_request_handle_controller_specific_errors(9)isci_io_request_build(9)
lowkey a whole friend group of functions fr fr β go say hi to all of them π
and that's the page!! mwah π this little number lives in ./drivers/scsi/isci, dated October 2026, and it's filed under sci_req_tx_bytes(9) β slay, periodt, go read your kernel source π§ββοΈβ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms