target: don't limit transfer sizes for the ramdisk backend
authorChristoph Hellwig <hch@infradead.org>
Mon, 26 Mar 2012 08:57:08 +0000 (04:57 -0400)
committerNicholas Bellinger <nab@linux-iscsi.org>
Sun, 15 Apr 2012 00:40:30 +0000 (17:40 -0700)
The ramdisk backend has not inherent limitations for handling requests,
so don't artificially limits the transfer size.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
drivers/target/target_core_rd.c
drivers/target/target_core_rd.h

index 2a89187d262c13c173ddd2920f3c8a4d0feb2b62..35c64d1e09d9c5cf58db0b4fb2a0225c5c9cf05a 100644 (file)
@@ -64,9 +64,6 @@ static int rd_attach_hba(struct se_hba *hba, u32 host_id)
        pr_debug("CORE_HBA[%d] - TCM Ramdisk HBA Driver %s on"
                " Generic Target Core Stack %s\n", hba->hba_id,
                RD_HBA_VERSION, TARGET_CORE_MOD_VERSION);
-       pr_debug("CORE_HBA[%d] - Attached Ramdisk HBA: %u to Generic"
-               " MaxSectors: %u\n", hba->hba_id,
-               rd_host->rd_host_id, RD_MAX_SECTORS);
 
        return 0;
 }
@@ -235,8 +232,8 @@ static struct se_device *rd_create_virtdevice(struct se_hba *hba,
        snprintf(rev, 4, "%s", RD_MCP_VERSION);
 
        dev_limits.limits.logical_block_size = RD_BLOCKSIZE;
-       dev_limits.limits.max_hw_sectors = RD_MAX_SECTORS;
-       dev_limits.limits.max_sectors = RD_MAX_SECTORS;
+       dev_limits.limits.max_hw_sectors = UINT_MAX;
+       dev_limits.limits.max_sectors = UINT_MAX;
        dev_limits.hw_queue_depth = RD_MAX_DEVICE_QUEUE_DEPTH;
        dev_limits.queue_depth = RD_DEVICE_QUEUE_DEPTH;
 
index 94acec9e872fbd6f11930e1af4abbbdbdf45f776..21458125fe512fcdf2b54cfe4d4801ebf630535d 100644 (file)
@@ -9,7 +9,6 @@
 #define RD_DEVICE_QUEUE_DEPTH  32
 #define RD_MAX_DEVICE_QUEUE_DEPTH 128
 #define RD_BLOCKSIZE           512
-#define RD_MAX_SECTORS         1024
 
 /* Used in target_core_init_configfs() for virtual LUN 0 access */
 int __init rd_module_init(void);