Chris Worley, on 10/28/2009 09:47 PM wrote:
It appears that SRP tries to coalesce and fragment initiator I/O
requests into 64KB packets, as that looks to be the size requested
to/from the device on the target side (and the I/O scheduler is
disabled on the target).
Is there a way to control this, where no coalescing occurs when
latency is an issue and requests are small, and no fragmentation
occurs when requests are large?
Or, am I totally wrong in my assumption that SRP is coalescing/fragmenting data?
You can at any time see size of requests you are receiving on the target
side by either enabling "scsi" logging (hopefully, you know how to do
it) or by looking in /proc/scsi_tgt/sgv. In the latter file you will see
general statistics for power of 2 allocations, i.e. request for 10K will
increase 16K row.
Vlad
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
