ibmvscsi_get_desired_dma(9)
π ibmvscsi_get_desired_dma(9) π
Welcome to the Kernel API Manual, bestie! We're doing ibmvscsi_get_desired_dma today, and every single detail is staying right here β no cap. π¦β¨
πΈ NAME πΈ
ibmvscsi_get_desired_dma β Calculate IO memory desired by the driver. π
β¨ SYNOPSIS β¨
unsigned long ibmvscsi_get_desired_dma (struct vio_dev *vdev );
Lowkey just that one signature, and it's iconic. π«Ά
π ARGUMENTS π
vdevβstruct vio_devfor the device whose desired IO mem is to be returned. That's the device we're asking about, periodt. π
π DESCRIPTION π
The return value is the number of bytes of IO data the driver will need to perform well. π That's the whole story, bestie. β¨
π₯ SEE ALSO π₯
- Kernel file
./drivers/scsi/ibmvscsi/ibmvscsi.c ibmvscsi_handle_event(9)ibmvscsi_release_crq_queue(9)crq_queue_next_crq(9)ibmvscsi_send_crq(9)ibmvscsi_task(9)ibmvscsi_reset_crq_queue(9)ibmvscsi_init_crq_queue(9)ibmvscsi_reenable_crq_queue(9)initialize_event_pool(9)release_event_pool(9)valid_event_struct(9)free_event_struct(9)get_event_struct(9)init_event_struct(9)unmap_cmd_data(9)map_sg_data(9)map_data_for_srp_cmd(9)purge_requests(9)ibmvscsi_set_request_limit(9)ibmvscsi_reset_host(9)ibmvscsi_timeout(9)ibmvscsi_send_srp_event(9)handle_cmd_rsp(9)lun_from_dev(9)ibmvscsi_queuecommand_lck(9)map_persist_bufs(9)unmap_persist_bufs(9)login_rsp(9)send_srp_login(9)capabilities_rsp(9)send_mad_capabilities(9)fast_fail_rsp(9)enable_fast_fail(9)adapter_info_rsp(9)send_mad_adapter_info(9)ibmvscsi_eh_host_reset_handler(9)ibmvscsi_handle_crq(9)ibmvscsi_sdev_configure(9)ibmvscsi_change_queue_depth(9)ibmvscsi_resume(9)
And that's a wrap, bestie! π This page comes from source/version ./drivers/scsi/ibmvscsi, dated October 2026. Slay, bye! π
β¨
π¦ 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