Searched refs:latencies (Results 1 – 6 of 6) sorted by relevance
160 zfcp_sdev->latencies.write.channel.min = 0xFFFFFFFF; in zfcp_scsi_slave_alloc()161 zfcp_sdev->latencies.write.fabric.min = 0xFFFFFFFF; in zfcp_scsi_slave_alloc()162 zfcp_sdev->latencies.read.channel.min = 0xFFFFFFFF; in zfcp_scsi_slave_alloc()163 zfcp_sdev->latencies.read.fabric.min = 0xFFFFFFFF; in zfcp_scsi_slave_alloc()164 zfcp_sdev->latencies.cmd.channel.min = 0xFFFFFFFF; in zfcp_scsi_slave_alloc()165 zfcp_sdev->latencies.cmd.fabric.min = 0xFFFFFFFF; in zfcp_scsi_slave_alloc()166 spin_lock_init(&zfcp_sdev->latencies.lock); in zfcp_scsi_slave_alloc()
255 struct zfcp_latencies latencies; member
381 struct zfcp_latencies *lat = &zfcp_sdev->latencies; \412 struct zfcp_latencies *lat = &zfcp_sdev->latencies; \
2003 lat = &zfcp_sdev->latencies.read; in zfcp_fsf_req_trace()2008 lat = &zfcp_sdev->latencies.write; in zfcp_fsf_req_trace()2011 lat = &zfcp_sdev->latencies.cmd; in zfcp_fsf_req_trace()2016 spin_lock(&zfcp_sdev->latencies.lock); in zfcp_fsf_req_trace()2020 spin_unlock(&zfcp_sdev->latencies.lock); in zfcp_fsf_req_trace()
217 slowdowns and noticeable latencies. Normally Speedstep should be used
122 latencies that makes the VFS to appear bursty in a system with