On 06/09/2010 09:19 AM, Patrick J. LoPresti wrote:
Hi, Mike, and thank you for your reply.
On Tue, Jun 8, 2010 at 10:00 PM, Mike Christie wrote:
# To control how many commands the session will queue set
# node.session.cmds_max to an integer between 2 and 2048 that is also
# a power of 2. The
On Wed, Jun 9, 2010 at 7:19 AM, I wrote:
>
> First, why would I want cmds_max larger than queue_depth? Is it
> something to do with the protocol (e.g., a single command to the
> device can become multiple commands in the session)? Or is it just
> because one session can have multiple targets, whi
Hi, Mike, and thank you for your reply.
On Tue, Jun 8, 2010 at 10:00 PM, Mike Christie wrote:
>
> # To control how many commands the session will queue set
> # node.session.cmds_max to an integer between 2 and 2048 that is also
> # a power of 2. The default is 128.
> node.session.cmds_max = 128
>
On 06/08/2010 07:55 PM, Patrick J. LoPresti wrote:
I apologize if this is a dumb question, but I am new to iSCSI. (Well,
at this level of detail, I am new to SCSI in general.)
I have been browsing the source code (open-iscsi-2.0-871), and I am
curious about the following iscsid.conf parameters:
I apologize if this is a dumb question, but I am new to iSCSI. (Well,
at this level of detail, I am new to SCSI in general.)
I have been browsing the source code (open-iscsi-2.0-871), and I am
curious about the following iscsid.conf parameters:
node.session.initial_cmdsn
node.session.cmds_ma
