- 05 Sep, 2009 20 commits
-
-
Swen Schillig authored
The fc_rport structure reserves a reference where a LLD can put information required in a situation where the fc transport class is triggering LLD callbacks. The zfcp driver was using this variable directly which is discouraged. This patch solves this issue by making this reference unnecessary. In addition the dev_loss_tmo callback is removed, it is not required: zfcp does not access the fc_rport after calling fc_remote_port_delete. Signed-off-by:
Swen Schillig <swen@vnet.ibm.com> Signed-off-by:
Christof Schmitt <christof.schmitt@de.ibm.com> Signed-off-by:
James Bottomley <James.Bottomley@suse.de>
-
Swen Schillig authored
Update the Fibre Channel related code to use the zfcp_fc prefix. Signed-off-by:
-
Swen Schillig authored
Extract independent data structures and introduce common _setup and _destroy routines for QDIO and Fibre Channel related data structures Signed-off-by:
-
Swen Schillig authored
Change the dbf data and functions to use the zfcp_dbf prefix throughout the code. Also change the calls to dbf to use zfcp_dbf instead of zfcp_adapter. Signed-off-by:
-
Christof Schmitt authored
Don't let the erp wait for gid_pn requests to complete. Instead, queue the gid_pn work, exit erp and let the finished gid_pn work trigger a new port reopen. Reviewed-by:
-
Swen Schillig authored
The zfcp_adapter structure was growing over time to a size of almost one memory page. To reduce the size of the data structure and to seperate different layers, put all qdio related data in the new zfcp_qdio data structure. Signed-off-by:
-
Swen Schillig authored
Split all qdio related attributes out of zfcp_fsf_req and put it in new structure. Signed-off-by:
-
Swen Schillig authored
Remove the global driver work queue and replace it with a workqueue local to the adapter. The usage of this workqueue makes this the correct place for the structure. In addition multiple adapters won't block each other due to the serialization of the queued work. Signed-off-by:
-
Swen Schillig authored
The flag ZFCP_REQ_AUTO_CLEANUP was useless as the ZFCP_STATUS_FSFREQ_CLEANUP flag is there for exactly the same purpose. Signed-off-by:
-
Swen Schillig authored
Remove the special case for NO_QTCB requests and optimize the mempool and cache processing for fsfreqs. Especially use seperate mempools for the zfcp_fsf_req and zfcp_qtcb structs. Signed-off-by:
-
Swen Schillig authored
The combination wait_queue/wakeup in conjunction with the flag ZFCP_STATUS_FSFREQ_COMPLETED to signal the completion of an fsfreq was not race-safe and can be better solved by a completion. Signed-off-by:
-
Swen Schillig authored
There is no need for the QDIO layer to have knowledge or do things wich are done better by the FSF layer and vice versa. Straighten a few things to improve vividness. Signed-off-by:
-
Christof Schmitt authored
An adapter shutdown implicitly closes all open ports. Make sure to mark all WKA ports as offline, not only the directory server. Also make sure that no pending wka port work is running when the adapter is being removed. Reviewed-by:
-
Christof Schmitt authored
When the FCP channel returns a series of commands with the error status "test link", zfcp will send a series of ELS ADISC commands. This is technically no problem, but it is enough to only issue one test command per remote port. So, track whether a ELS ADISC command is already pending, and do not send a new one if there is already a pending command. Reviewed-by:
-
Christof Schmitt authored
Using a bitwise OR to not set anything at all is pointless so remove the useless statement. Reviewed-by:
-
Christof Schmitt authored
The default trace level is to only trace failed FSF commands. Thus it is not necessary to collect trace data for most FSF commands, since it will be thrown away later. Restructure the FSF/HBA trace infrastructure to first check the trace level in a inline function and only do the expensive data collection for matching trace levels. Reviewed-by:
-
Christof Schmitt authored
The default trace level is to only trace failed SCSI commands. Thus it is not necessary to collect trace data for most SCSI commands since it will be thrown away later. Restructure the SCSI trace infrastructure to first check the trace level in a inline function and only do the expensive data collection for matching trace levels. Reviewed-by:
-
Christof Schmitt authored
The struct zfcp_adapter includes everything related to the debug traces. This introduces dependences between the definitions in zfcp_def.h and zfcp_dbf.h. Move all debug related data structures to a new data structure to break those dependencies and manage the debug data in zfcp_dbf.[hc]. Reviewed-by:
-
Swen Schillig authored
In certain error scenarios ports, rports are getting attached, validated and removed from the systems environment. Depending on the layer this occurs asynchronously. This patch fixes the few races which existed and ensures all references and cross references are cleared at the time they're invalid. In addition fc transports actions are only scheduled when required. Signed-off-by:
-
Yanqing_Liu@Dell.com authored
This patch is to add DM support for next generation of Dell PowerVault storage array. Signed-off-by:
Yanqing Liu <Yanqing_Liu@Dell.com> Acked-by:
Chandra Seetharaman <sekharan@us.ibm.com> Signed-off-by:
-
- 22 Aug, 2009 20 commits
-
-
James Bottomley authored
Novell is now funding SCSI work, so the MAINTAINERS file should reflect this. Signed-off-by: -
Kashyap, Desai authored
Bump version to 3.04.11 Signed-off-by: -
Kashyap, Desai authored
Code cleanup of host page alloc and diag reset. Signed-off-by: -
Kashyap, Desai authored
Do not set max_id value received from FW. Once SAS transport layer is introduced max_id value is missleading to SCSI mid layer. Use max_id to infinite value. logic of can queue of scsi host is changed. Signed-off-by: -
Kashyap, Desai authored
Change config request timeout value to 30 seconds. Signed-off-by: -
Kashyap, Desai authored
Handle insufficient resources status as similar to busy status. Signed-off-by: -
Kashyap, Desai authored
Removed mptscsih_timer_expired. This timer is no more use. Signed-off-by: -
Kashyap, Desai authored
Change DEFINED value of can queue for FC and SAS devices. Signed-off-by: -
Chandra Seetharaman authored
Reported-by:
Rice Brown <rick.brown@oit.gatech.edu> Signed-Off-by:
-
James Bottomley authored
Universally, SCSI functions assume the lengths fed in are those of the buffer to DMA data to, not the lengths of the data minus the header. scsi_vpd_inquiry() assumed the latter and got it wrong, so fix up all the functions to use the correct assumption (and fix a bug where INQUIRY in SCSI-2 dcannot go over 255). [jejb: Matthew posted an identical version of this at the same time I did] Signed-off-by:
Matthew Wilcox <matthew@wil.cx> Signed-off-by:
-
Michael Reed authored
An IBM tape drive failed to complete a PERSISTENT RESERVE IN within the scsi cmd timeout. Error recovery was initiated and it sequenced from abort through taking the tape drive offline. The device was taken offline because it repeatedly responded to the TUR command issued by error recovery with a RESERVATION CONFLICT status. The tape drive was reserved to another system. This is perfectly legitimate response to TUR, and is one that an escalation of recovery is unlikely to clear. Further, escalation of recovery can have undesirable side effects on the operation of tape drives shared with other initiators. Instead of escalating recovery, error recovery should treat the RESERVATION CONFLICT response to the TUR as a good status, giving the issuer of the command the opportunity to handle the timeout and reservation conflict. Signed-off-by:
Michael reed <mdr@sgi.com> Signed-off-by:
-
Jiri Slaby authored
In nsp_cs_config there is a wrong struct nsp_cs_configdata allocation. It allocates only sizeof(pointer to nsp_cs_configdata) for a whole structure. Add a dereference to the sizeof to allocate sizeof(nsp_cs_configdata). Signed-off-by:
Jiri Slaby <jirislaby@gmail.com> Signed-off-by:
-
Davidlohr Bueso A authored
Verify that ch->dt is not NULL before using it. Signed-off-by:
Davidlohr Bueso <dave@gnu.org> Signed-off-by:
-
Sage Weil authored
The allocated struct is manually zeroed after allocation, so avoid using the (broken) kzalloc mempool (which does not re-zero previously used items when they are returned to the pool). Acked-by:
Brian King <brking@linux.vnet.ibm.com> Signed-off-by:
Sage Weil <sage@newdream.net> Signed-off-by:
-
Giridhar Malavali authored
Signed-off-by:
Giridhar Malavali <giridhar.malavali@qlogic.com> Signed-off-by:
James Bottomley <James.Bottomley@HansenPartnership.com> Signed-off-by:
-
Anirban Chakraborty authored
When the multiqueue mode fails to work, the driver falls back on single queue mode. This ensures that the firmware is reinitialized with single queue options and all the resources are readjusted accordingly. Signed-off-by:
Anirban Chakraborty <anirban.chakraborty@qlogic.com> Signed-off-by:
-
Andrew Vasquez authored
Signed-off-by:
Andrew Vasquez <andrew.vasquez@qlogic.com> Signed-off-by:
-
Anirban Chakraborty authored
The interrupt handler clears the interrupt status register for response updates in the base queue while working in the multique mode. This could lead to missing interrupt for async events, mail box completions etc. as these are also handled in the base queue. The fix ensures that the interrupt bit is not cleared for response updates in the ISR when the driver is working in multiqueue mode. Signed-off-by:
-
Andrew Vasquez authored
Signed-off-by:
-
Shyam Sundar authored
One byte added to make the IOCB structure satisfy size requirements. Signed-off-by:
Shyam Sundar <shyam.sundar@qlogic.com> Signed-off-by:
-
