[PATCH qla4xxx] implement qla4xxx conn and sess set param

[Mike Christie]

This patch just has qla4xxx implement the basic set param attrs like
connection address and port, target portal group tag, and target name.
Like send targets, it does not support ipv6 because I am not sure what
bits to be testing and setting. I guess that can be done later in a fix
up patch. I also do not have ipv6 setup so I would not know if it works
anyways.

One weird issue is that open-iscsi exposes the address we are currently
logged into. And we expose, what we call the persistent address and
port. These values are the initial values we use for login and in case
of a redirect the persistent and current values would be different.

I do not see how to get the different values for qla4xxx. And what is
the dev_db_entry->targetAddr? The dev_db_entry->ipAddr looks like the
address of the portal we are logged into, and dev_db_entry->targetAddr
was always zero.

[ravianand]

>On Sat, 24 Jun 2006, Mike Christie wrote:
> This patch just has qla4xxx implement the basic set param attrs like
> connection address and port, target portal group tag, and target name.
> Like send targets, it does not support ipv6 because I am not sure what
> bits to be testing and setting. I guess that can be done later in a fix
> up patch. I also do not have ipv6 setup so I would not know if it works
> anyways.

To my knowledge ISP4010/ISP4022 does not support IPV6.

>
> One weird issue is that open-iscsi exposes the address we are currently
> logged into. And we expose, what we call the persistent address and
> port. These values are the initial values we use for login and in case
> of a redirect the persistent and current values would be different.
>
> I do not see how to get the different values for qla4xxx.

Will let you know if there is a way to get it. I think there is,
but need to check.

>And what is
> the dev_db_entry->targetAddr?

The value stored in this field is the Target Address recieved from the target
by the ISP4XXX during login.

The dev_db_entry->ipAddr looks like the
> address of the portal we are logged into,

Thats true.

>and dev_db_entry->targetAddr
> was always zero.

I guess its always zero, since the info is not populated from the fw ddb entry.

Ravi