tcm_loop: bump max_sectors

There is not reason to artifically limit max_sectors in tcm_loop, set
it to UINT_MAX to allow stressing the large I/O handling in the target
core using the loopback driver.  Also remove various superflous defines
hiding the values set in the host template.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>

1 files changed, 4 insertions, 4 deletions

diff --git a/drivers/target/loopback/tcm_loop.c b/drivers/target/loopback/tcm_loop.c
index 572d27a6b7ae..c47ff7f59e57 100644
--- a/drivers/target/loopback/tcm_loop.c
+++ b/drivers/target/loopback/tcm_loop.c
@@ -416,11 +416,11 @@ static struct scsi_host_template tcm_loop_driver_template = {
         .queuecommand           = tcm_loop_queuecommand,
         .change_queue_depth     = tcm_loop_change_queue_depth,
         .eh_device_reset_handler = tcm_loop_device_reset,
-        .can_queue              = TL_SCSI_CAN_QUEUE,
+        .can_queue              = 1024,
         .this_id                = -1,
-        .sg_tablesize           = TL_SCSI_SG_TABLESIZE,
-        .cmd_per_lun            = TL_SCSI_CMD_PER_LUN,
-        .max_sectors            = TL_SCSI_MAX_SECTORS,
+        .sg_tablesize           = 256,
+        .cmd_per_lun            = 1024,
+        .max_sectors            = 0xFFFF,
         .use_clustering         = DISABLE_CLUSTERING,
         .slave_alloc            = tcm_loop_slave_alloc,
         .slave_configure        = tcm_loop_slave_configure,