summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authormav <mav@FreeBSD.org>2011-12-28 22:49:28 +0000
committermav <mav@FreeBSD.org>2011-12-28 22:49:28 +0000
commit43f4edf7203f4c4f56b79c3db477b3461cab0778 (patch)
treec155edca0406c05fbbd0f1ec1377bcbb1db85bf1
parent96d2ec96a9b060c1c15dfcf3347e79bcf61cba8a (diff)
downloadFreeBSD-src-43f4edf7203f4c4f56b79c3db477b3461cab0778.zip
FreeBSD-src-43f4edf7203f4c4f56b79c3db477b3461cab0778.tar.gz
Set maximum I/O size for mps(4) to MAXPHYS. Looking into the code, I see
no reason why it should be limited to 64K of DFLTPHYS. DMA data tag is any way set to allow MAXPHYS, S/G lists (chain elements) are sufficient and overflows are also handled. On my tests even 1MB I/Os are working fine. Reviewed by: ken@
-rw-r--r--sys/dev/mps/mps_sas.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/sys/dev/mps/mps_sas.c b/sys/dev/mps/mps_sas.c
index cf4757a..c253ee0 100644
--- a/sys/dev/mps/mps_sas.c
+++ b/sys/dev/mps/mps_sas.c
@@ -937,6 +937,7 @@ mpssas_action(struct cam_sim *sim, union ccb *ccb)
cpi->transport_version = 0;
cpi->protocol = PROTO_SCSI;
cpi->protocol_version = SCSI_REV_SPC;
+ cpi->maxio = MAXPHYS;
cpi->ccb_h.status = CAM_REQ_CMP;
break;
}
OpenPOWER on IntegriCloud