fnic: NoFIP solicitation frame in NONFIP mode and changed IO Throttle count
authorHiral Shah <hishah@cisco.com>
Fri, 18 Apr 2014 19:28:17 +0000 (12:28 -0700)
committerChristoph Hellwig <hch@lst.de>
Mon, 19 May 2014 11:32:51 +0000 (13:32 +0200)
commitc8ff03c6da96850e19fcaf359d1ae408308ad9d0
treee1220929e5e5639f460f6e4515420d76491772cb
parent13c3dde23f571072ef8c427ba18ec77e7b5bf5aa
fnic: NoFIP solicitation frame in NONFIP mode and changed IO Throttle count

This patch contains following three minor fixes.

1) During Probe, fnic was sending FIP solicitation in Non FIP mode which is not
   expected, setting the internal fip state to Non FIP mode explicitly, avoids
   sending FIP frame.

2) When target goes offline, all outstanding IOs belong to the target will be
   terminated by driver, If the termination count is high, then it influences
   firmware responsiveness. To improve the responsiveness, default IO throttle
   count is reduced to 256.

3) Accessing Virtual Fabric Id (vfid) and fc_map of Fibre-Channel Forwarder(FCF)
   is invalid in fnic driver when Clear Virtual Link(CVL) is received prior to
   receiving flogi reject from switch. As CVL clears all FCFs.

Signed-off-by: Hiral Shah <hishah@cisco.com>
Signed-off-by: Sesidhar Baddela <sebaddel@cisco.com>
Signed-off-by: Narsimhulu Musini <nmusini@cisco.com>
Signed-off-by: Anantha Tungarakodi <atungara@cisco.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
drivers/scsi/fnic/fnic.h
drivers/scsi/fnic/fnic_fcs.c
drivers/scsi/fnic/fnic_main.c