Gitweb:     
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=fff09a8e6e726f0752254e1f46f7224e3bebb302
Commit:     fff09a8e6e726f0752254e1f46f7224e3bebb302
Parent:     8cba2077325b361dedf058c7dfc6c33691422497
Author:     David Dillow <[EMAIL PROTECTED]>
AuthorDate: Wed Dec 19 17:09:15 2007 -0500
Committer:  Roland Dreier <[EMAIL PROTECTED]>
CommitDate: Fri Jan 25 14:15:37 2008 -0800

    IB/srp: Enable SG list chaining
    
    By default, the SCSI mid-layer seems to send down 512KB requests
    (sg_tablesize = 256), with some requests occasionally combined. By
    allowing the mid-layer to chain requests, we can easily grow to 1024KB
    or larger -- I've tested 4096KB I/O requests with no problems.
    
    I looked through the DMA paths on the hardware drivers to ensure they
    could take advantage of the SG chaining, and it seems that every one
    except ipath uses the system's DMA routines, which have been converted
    to handle chaining.  ipath looks like it should be OK, but I have no
    way to test it.
    
    Signed-off-by: David Dillow <[EMAIL PROTECTED]>
    
    [ Tested on ipath.  - Roland ]
    
    Signed-off-by: Roland Dreier <[EMAIL PROTECTED]>
---
 drivers/infiniband/ulp/srp/ib_srp.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/drivers/infiniband/ulp/srp/ib_srp.c 
b/drivers/infiniband/ulp/srp/ib_srp.c
index e98d061..66dade7 100644
--- a/drivers/infiniband/ulp/srp/ib_srp.c
+++ b/drivers/infiniband/ulp/srp/ib_srp.c
@@ -1548,6 +1548,7 @@ static struct scsi_host_template srp_template = {
        .this_id                        = -1,
        .cmd_per_lun                    = SRP_SQ_SIZE,
        .use_clustering                 = ENABLE_CLUSTERING,
+       .use_sg_chaining                = ENABLE_SG_CHAINING,
        .shost_attrs                    = srp_host_attrs
 };
 
-
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to