ibmvscsis_send_messages(9)
π ibmvscsis_send_messages π
okay bestie, welcome to the ibmvscsis_send_messages page β that's a section 9 (kernel API) manpage, and honestly? it's short, it's sweet, and it slaps. let's get into it π«Ά
β¨ NAME β¨
ibmvscsis_send_messages β literally just Send a Response. that's the whole vibe. π
πΈ SYNOPSIS πΈ
void ibmvscsis_send_messages (struct scsi_info *vscsi );
bestie it returns void. nothing comes back. it just does the thing. iconic behaviour honestly π
π ARGUMENTS π
vscsiβ a pointer to our adapter structure. yes, ours, we're claiming it. this is the main character struct and it has main character energy π
π¦ DESCRIPTION π¦
okay so here's what's going down: this function sends a response, but first it checks the waiting queue. considerate queen behaviour. it does a lil vibe check on the queue before it commits, yk? π
and the ordering? responses are sent in the order they are received. first in, first out, no cutting the line, no queue-jumping, we are civilised here β¨
now the sad part π β if the response can't be sent because the client queue is full? it doesn't get yeeted into the void. it just stays on the waiting queue, chilling, waiting for its moment. it'll get its turn. we believe in it π§
β οΈ PRECONDITION, bestie, read this one: called with the interrupt lock held. no cap, don't call it without that lock or you're gonna have a bad time π
π SEE ALSO π
the whole friend group, fr fr β go peep these:
first up, the actual source, our home base π :
Kernel file ./drivers/scsi/ibmvscsi_tgt/ibmvscsi_tgt.c
and then the extended fam, all section 9:
connection_broken(9)ibmvscsis_unregister_command_q(9)ibmvscsis_delete_client_info(9)ibmvscsis_free_command_q(9)ibmvscsis_cmd_q_dequeue(9)ibmvscsis_send_init_message(9)ibmvscsis_check_init_msg(9)ibmvscsis_disconnect(9)ibmvscsis_post_disconnect(9)ibmvscsis_handle_init_compl_msg(9)ibmvscsis_handle_init_msg(9)ibmvscsis_init_msg(9)ibmvscsis_establish_new_q(9)ibmvscsis_reset_queue(9)ibmvscsis_free_cmd_resources(9)ibmvscsis_ready_for_suspend(9)ibmvscsis_trans_event(9)ibmvscsis_poll_cmd_q(9)ibmvscsis_free_cmd_qs(9)ibmvscsis_get_free_cmd(9)ibmvscsis_adapter_idle(9)ibmvscsis_copy_crq_packet(9)ibmvscsis_adapter_info(9)ibmvscsis_cap_mad(9)ibmvscsis_process_mad(9)srp_snd_msg_failed(9)ibmvscsis_mad(9)ibmvscsis_login_rsp(9)ibmvscsis_srp_login_rej(9)ibmvscsis_srp_login(9)ibmvscsis_srp_i_logout(9)ibmvscsis_ping_response(9)ibmvscsis_parse_command(9)ibmvscsis_parse_cmd(9)ibmvscsis_parse_task(9)ibmvscsis_service_wait_q(9)ibmvscsis_enable_change_state(9)ibmvscsis_create_command_q(9)ibmvscsis_destroy_command_q(9)srp_build_response(9)ibmvscsis_handle_crq(9)
like, that's a whole squad. iykyk π«Ά
and that's the page!! short, adorable, gets the job done β a true 10/10 no notes moment β
sign-off time π this lil beauty lives in ./drivers/scsi/ibmvscsi_tgt, it's dated October 2026, and yes the title is still ibmvscsis_send_messages(9) because we could never forget her π slay, bye bestie! πβ¨
π¦ 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