- 08 Nov, 2016 40 commits
-
-
Arnd Bergmann authored
A recent bugfix introduced a harmless warning in the lpfc driver: drivers/scsi/lpfc/lpfc_init.c: In function 'lpfc_write_firmware': drivers/scsi/lpfc/lpfc_logmsg.h:56:45: error: format '%ld' expects argument of type 'long int', but argument 9 has type 'size_t {aka const unsigned int}' [-Werror=format=] 'size_t' is always the same width as 'long' in the kernel, but the compiler doesn't know that. The %z modifier is what the standard expects to be used here, and this shuts up the warning. Fixes: 679053c651fb ("scsi: lpfc: Fix fw download on SLI-4 FC adapters") Signed-off-by:Arnd Bergmann <arnd@arndb.de> Reviewed-by:
Johannes Thumshirn <jthumshirn@suse.de> Acked-by:
James Smart <james.smart@broadcom.com> Signed-off-by:
Martin K. Petersen <martin.petersen@oracle.com>
-
Hannes Reinecke authored
Any multicase address is set on all interfaces, the base interface and any VLAN interfaces on top of this. So we might receive frames which are not destined for us. Signed-off-by:
Hannes Reinecke <hare@suse.de> Reviewed-by:
Bart Van Assche <bart.vanassche@sandisk.com> Signed-off-by:
-
Hannes Reinecke authored
The FIP VLAN frame consists of an ethernet header followed by the FIP VLAN frame, so we need to skip the ethernet header if we want to check the FIP opcode. Signed-off-by:
Hannes Reinecke <hare@suse.com> Reviewed-by:
-
Hannes Reinecke authored
Add additional statements for debugging FIP frames. Signed-off-by:
-
Hannes Reinecke authored
The 'enabled' sysfs attribute only accepts the values '0' and '1', so we should error out any other values. Signed-off-by:
Johannes Thumshirn <jth@kernel.org> Signed-off-by:
-
Hannes Reinecke authored
If DCB is not enabled or compiled in we still should be setting a sane default priority. So put FCoE frames in priority class 'interactive' and FIP frames in priority class 'besteffort'. Signed-off-by:
-
Hannes Reinecke authored
We currently can only lookup the local xid, so we need to reject REC with empty rxid. Signed-off-by:
-
Hannes Reinecke authored
When detecting an out-of-order sequence we should be waiting for E_D_TOV before trying to abort the sequence. The response might still be stuck in the queue somewhere. Signed-off-by:
-
Hannes Reinecke authored
When we're receiving a timeout we should be checking for queue full status; if there are still some packets pending we should be resetting the counter to ensure we're not missing out any packets which are still queued. Signed-off-by:
-
Hannes Reinecke authored
When receiving packets from the network we cannot guarantee any frame ordering, so we should be receiving all valid frames and let the upper layers deal with it. Signed-off-by:
-
Hannes Reinecke authored
If a sequence should be aborted the exchange might already be completed (eg if the response is still queued in the rx queue), so this shouldn't considered as an error. Signed-off-by:
-
Hannes Reinecke authored
When a sequence times out we have no idea what happened to the frame. And we do not know if we will ever receive the frame. Hence we cannot re-use the xid as we would risk data corruption if the xid had been re-used and the timed out frame would be received after that. So we need to quarantine the xid until the lport is reset. Yes, I know this will (eventually) deplete the xid pool. But for now it's the safest method. Signed-off-by:
-
Hannes Reinecke authored
The cached exchange index might be invalid, in which case we should drop down to allocate a new one. And we should not try to access an invalid exchange when responding to a BA_ABTS. Signed-off-by:
-
Hannes Reinecke authored
When the queue depth is reduced we should print out the reason for this; it might be due to a queue full condition. Signed-off-by:
-
Hannes Reinecke authored
Occasionally it might happen that we receive a PRLI while we're still waiting for our PLOGI response. In that case we should return 'busy' LS status instead of 'plogi required' LS status. Signed-off-by:
-
Hannes Reinecke authored
PRLI is only required if the port is acting as an initiator; ports which support target functionality only do not need to send PRLI. At the same time the PRLI state is only used if the port initiated a PRLI transfer; if we received a PRLI request we should _not_ change the state as this would cause our PRLI response to be dropped. And when we receive a PRLI response we need to check if an image pair has been established; if not the remote port cannot act as a target for us and we need to disable target functionality. Signed-off-by:
-
Hannes Reinecke authored
The libfc stack generates an RTV request, so we should be implementing an RTV responder, too. Signed-off-by:
-
Hannes Reinecke authored
We only ever use the 'fp' argument for fc_rport_error() to encapsulate the error code, so we can as well do away with that and pass the error directly. Signed-off-by:
-
Hannes Reinecke authored
When a command is aborted it might already have the DID_TIME_OUT status set, so we shouldn't be overwriting that. Signed-off-by:
-
Hannes Reinecke authored
The user might want to modify the values for R_A_TOV and E_D_TOV, so add new module parameters 'e_d_tov' and 'r_a_tov' for the 'fcoe' modules and allow to modify them via sysfs attributes. Signed-off-by:
-
Hannes Reinecke authored
When setting the FCP timeout we need to ensure a lower boundary for E_D_TOV and R_A_TOV, otherwise we'd be getting spurious I/O issues due to the fcp timer firing too early. Signed-off-by:
-
Hannes Reinecke authored
If fc_rport_error_retry() is attempting to retry the remote port state we should be waiting for the configured e_d_tov value rather than the default. Signed-off-by:
-
Hannes Reinecke authored
We should be using the configured R_A_TOV value when sending the exchange. Signed-off-by:
-
Hannes Reinecke authored
If a command times out libfc is sending an REC, which also might fail (due to frames being lost or something). If no data has been transferred we can simply retry the command, but the current code sets a state of FC_ERROR, which then is being translated into DID_ERROR, resulting in an I/O error. So to handle this properly we need to set a separate state FC_TRANS_RESET and mapping it onto DID_SOFT_RETRY. Signed-off-by:
-
Hannes Reinecke authored
Signed-off-by:
-
Martin K. Petersen authored
This reverts commit 3e22760d. This revert came about because of efforts by Ewan Milne, Curtis Taylor and I. In researching this issue, significant performance issues were seen on large CPU count systems using the software FCOE stack. Hannes also weighed in. The same was not apparent on much smaller low count CPU systems. The behavior introduced by commit 3e22760d lands sup with large count CPU systems seeing continual blk_requeue_request() calls due to ML_QUEUE_HOST_BUSY. fc_exch_alloc() used to try all the available exchange managers in the list for an available exchange id, but this was changed in 2010 so that if the first matched exchange manager couldn't allocate one, it fails and we end up returning host busy. This was due to commit: Setting the ddp_min module parameter to fcoe to 128MB prevents the ->match function from permitting the use of the offload exchange manager for the frame, and we no longer see the problem with host busy status, since it uses the larger non-offloaded pool. Reverting commit 3e22760d was tested to also prevent the host busy issue due to failing allocations. Suggested-by:
Ewan Milne <emilne@redhat.com> Suggested-by:
Curtis Taylor <cjt@us.ibm.com> Tested-by:
Laurence Oberman <loberman@redhat.com> Signed-off-by:
-
James Smart authored
lpfc version changed to 11.2.0.2 Signed-off-by:
Dick Kennedy <dick.kennedy@broadcom.com> Signed-off-by:
-
James Smart authored
Fix fw download on SLI-4 FC adapters Driver performs a quick validation of magic numbers in the fw download image. Driver needed to be updated for more recent magic numbers. Signed-off-by:
-
James Smart authored
Synchronize link speed with boot driver Link speed settings set by the boot driver are reported by the hw. Driver will attempt to read them, and if set, will respect their values. The driver can override the settings with its own if instructed by user space (via bsg), with the new values being picked up by the boot driver. Signed-off-by:
-
James Smart authored
Correct panics with eh_timeout and eh_deadline We were having double completions on our SLI-3 version of adapters. Solved by clearing our command pointer before calling scsi_done. The eh paths potentially ran simulatenously and would see the non-null value and invoke scsi_done again. Signed-off-by:
-
James Smart authored
Fix lost target in pt-to-pt connect Change reject code to something that allows a retry Signed-off-by:
-
James Smart authored
Revise strings with full lpfc parameter name Signed-off-by:
-
James Smart authored
Code cleanup for lpfc_sriov_nr_virtfn parameter Signed-off-by:
-
James Smart authored
Code cleanup for lpfc_max_scsicmpl_time parameter Signed-off-by:
-
James Smart authored
Code cleanup for lpfc_topology parameter Signed-off-by:
-
James Smart authored
Code cleanup for lpfc_aer_support parameter Signed-off-by:
-
James Smart authored
Code cleanup for lpfc_enable_rrq parameter Signed-off-by:
-
James Smart authored
Code clean up for lpfc_iocb_cnt parameter Signed-off-by:
-
James Smart authored
Make lpfc_prot_mask and lpfc_prot_guard per hba parameters Signed-off-by:
-
James Smart authored
Set driver environment data on adapter Signed-off-by:
-
