Re: Max Target Count Limit

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Nick,
I went through the source in a little more detail and figured out why I was hitting the 256 target count limit.  The addlun operation was failing on LUN# 256.   I just found the 256 LUNs per PG limit in target_core_base.h.

Thanks,
-Joe




----- Original Message -----
From: Nicholas A. Bellinger <nab@xxxxxxxxxxxxxxx>
To: jrepac@xxxxxxxxx
Cc: "target-devel@xxxxxxxxxxxxxxx" <target-devel@xxxxxxxxxxxxxxx>
Sent: Thursday, December 15, 2011 11:49 PM
Subject: Re: Max Target Count Limit

On Thu, 2011-12-15 at 19:15 -0800, jrepac@xxxxxxxxx wrote:
> Are there any downsides to increasing the maximum target count limit currently set at 256?
> 
> #define FD_MAX_DEV_NAME        256
> 
> I was thinking of increasing it for testing to 1024.
> 

Hi Joe,

FD_MAX_DEV_NAME is used to limit the 'fd_dev_name' path-name size for
FILEIO backends, and is not related to a maximum target count limit.

The current value of 256 bytes is fairly arbitrary, and using 1024 (or
anything else that is a PAGE_SIZE or below) should be OK.

--nab
--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux SCSI]     [Kernel Newbies]     [Linux SCSI Target Infrastructure]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Device Mapper]

  Powered by Linux