- 14 Jan, 2006 40 commits
-
-
andrew.vasquez@qlogic.com authored
Signed-off-by:
Andrew Vasquez <andrew.vasquez@qlogic.com> Signed-off-by:
James Bottomley <James.Bottomley@SteelEye.com>
-
andrew.vasquez@qlogic.com authored
Given the semantic changes in both the device-model and fc-transport APIs, the driver's handling of port-type RSCNs via a series of ADISCs and PLOGIs can cause series of badness ranging from unexpectedly device loss to devices not being discovered. In the interim, disable (via a module-parameter) this feature and allow RSCN management to continue to occur within the driver's DPC thread. Signed-off-by:
-
andrew.vasquez@qlogic.com authored
Signed-off-by:
-
andrew.vasquez@qlogic.com authored
Signed-off-by:
-
andrew.vasquez@qlogic.com authored
Similarly to other ISPs, set execution throttle to maximum allowed value since 'throttling' is done on a per-lun basis via queue-depth. Signed-off-by:
-
andrew.vasquez@qlogic.com authored
Simplify essentially duplicate load RISC RAM implementation in qla2x00_load_ram_ext() and qla2x00_load_ram(). Signed-off-by:
-
andrew.vasquez@qlogic.com authored
Swing/emphasis settings in NVRAM were not being honoured due to the driver not converting the serial-link options from LE to host-endian format. Signed-off-by:
-
andrew.vasquez@qlogic.com authored
If the Get Port Database call fails during local-loop update, then schedule the DPC routine to perform a rescan as the firmware would have updated the Get ID List port-entries of their new state. Signed-off-by:
-
andrew.vasquez@qlogic.com authored
Small changes to register retrieval and order as per latest firmware specification. Signed-off-by:
-
andrew.vasquez@qlogic.com authored
Driver would not correctly re-enable the write-protection bits of the flash part after updates. Signed-off-by:
-
andrew.vasquez@qlogic.com authored
Problem report (against 2.4.x driver) from Jeff Layton <jlayton@redhat.com>: An OEM noticed that the U6 qla2200 driver would hang for around 2 minutes at boot time and then proceed normally. I found that the delay was occurring when loading the new firmware into the card, and was due to a schedule_timeout(10) added to the bottom of the polling loop. Some testing showed that the load ram operation on the card was very quick (on the order of a couple of jiffies), but the sleep in the polling loop was making each operation take around 25-30. The attached patch corrects this by making it skip sleeping during the load ram operation, since I believe we only do that when the module is plugged in. It also skips sleeping if the mbox_int flag got set during the current loop. This corrected the hang on my test setup, and OEM also confirmed that it corrected the problem for them. Signed-off-by:
-
andrew.vasquez@qlogic.com authored
Mailbox commands are polled for completion during ISP initialization. During potentially 'long' mailbox commands (i.e. fabric login), we really don't want a busy-wait delay to potentially trigger a (benign) soft-lockup BUG(). Signed-off-by:
-
andrew.vasquez@qlogic.com authored
There's no point in displaying the message during a valid underrun case. Limit the message to potentially problematic cases. Signed-off-by:
-
andrew.vasquez@qlogic.com authored
Signed-off-by:
-
andrew.vasquez@qlogic.com authored
The initial-control-block references are not always correct as the use-node-name qualifier during NVRAM configuration will cause the firmware to use the portname as a base for the nodename. Signed-off-by:
-
Mike Christie authored
From: FUJITA Tomonori <tomof@acm.org> and zhenyu.z.wang@intel.com: We cannot handle filesystems like XFS becuase of the pages they are sending us. We had thought page_count could be used to work around this, but the correct test is for PageSlab. The proper solution is to figure out what type of pages filesystems can use so we do not have to add tests like this or handle it in the block layer for all network block drivers but the issue still has not been resolved on fs-devel so we are sending this patch as a temporary fix. This is last patch just in case it is Nakd with the explanation that we need to push the correct fix through fs-devel, mm or the block layer. The rest of the patchset can live without the patch, but the driver will not work with filesystems like XFS. Signed-off-by:
Alex Aizman <itn780@yahoo.com> Signed-off-by:
Dmitry Yusupov <dmitry_yus@yahoo.com> Signed-off-by:
Mike Christie <michaelc@cs.wisc.edu> Signed-off-by:
-
Mike Christie authored
When we run the xmit code from queuecomand the stack trace gets too deep. The patch runs the xmit code from the scsi_host work queue. This fixes 4k stack and xfs support and should fix the st and sg stack usage bugs. Signed-off-by:
-
Mike Christie authored
This is the second version of the patch to address Christoph's comments. Instead of doing the lib, I just kept everything in scsi_trnapsort_iscsi.c like the FC and SPI class. This was becuase the driver model and sysfs class is tied to the session and connection setup so separating did not buy very much at this time. The reason for this patch was becuase HW iscsi LLDs like qla4xxx cannot use the iscsi class becuase the scsi_host was tied to the interface and class code. This patch just seperates the session from scsi host so that LLDs that allocate the host per some resource like pci device can still use the class. This is also fixes a couple refcount bugs that can be triggered when users have a sysfs file open, close the session, then read or write to the file. Signed-off-by:
-
Mike Christie authored
From Mike Christie <michaelc@cs.wisc.edu> and FUJITA Tomonori <tomof@acm.org>: We cannot use page_address becuase some pages could be highmem. Instead, we can use sock_no_sendpage which does kmap for us. Signed-off-by:
-
FUJITA Tomonori authored
Users can write to a page while we are sending it and making digest calculations. This ends up causing us to retry the command when a digest error is later reported. By using sock_no_sendpage when data digests are calculated we can avoid a lot of (not all but it helps) the retries becuase sock_no_sendpage is not zero copy. Signed-off-by:
-
zhenyu.z.wang@intel.com authored
We should be taking the host_lock instead of the conn lock when checking host_busy. Signed-off-by:
-
zhenyu.z.wang@intel.com authored
We need to check the ISCSI_FLAG_DATA_* flags. Signed-off-by:
-
FUJITA Tomonori authored
Remove extra whitespaces. Signed-off-by:
-
Jes Sorensen authored
Convert a the 3w-9xxx.c and 3w-xxxx.c drivers to use mutexes instead of semaphores. Untested, but compiles and looks obviously correct. Signed-off-by:
Jes Sorensen <jes@sgi.com> Signed-off-by:
-
James Bottomley authored
Now that mptfc actually uses the transport class, it can't be built without it. Signed-off-by: -
Moore, Eric authored
The fix is to write 'MPI_HIM_DIM' to the Host Interrupt Mask register, when enabling interrupts. Instead of the tilde of MPI_HIM_RIM. Apparently writing '1's to some of the reserved bits was causing all the bits to go to `1`, which effectly disabled all interrupts. Signed-off-by:
Eric Moore <Eric.Moore@lsil.com> Signed-off-by:
-
Moore, Eric authored
We will be mapping the RAID volumes in mptsas to a reserved channel that is one larger than the anticapated number of ports on the direct attached host adapter. Signed-off-by:
-
Moore, Eric authored
This updates mpi headers in fusion drivers to version 1.5.12. Signed-off-by:
-
Moore, Eric authored
The SAS RAID volumes are reported beyond the expected number of phys. Signed-off-by:
-
Christoph Hellwig authored
When James Smart fixed the issue of the userspace scan atributes crashing the system with the FC transport class he added a patch to let the transport class check if the parent is valid for a given transport class. When adding support for the integrated raid of fusion sas devices we ran into a problem with that, as it didn't allow adding virtual raid volumes without the transport class knowing about it. So this patch adds a user_scan attribute instead, that takes over from scsi_scan_host_selected if the transport class sets it and thus lets the transport class control the user-initiated scanning. As this plugs the hole about user-initiated scanning the target_parent hook goes away and we rely on callers of the scanning routines to do something sensible. For SAS this meant I had to switch from a spinlock to a mutex to synchronize the topology linked lists, in FC they were completely unsynchronized which seems wrong. Signed-off-by:
Christoph Hellwig <hch@lst.de> Signed-off-by:
-
Moore, Eric authored
Add software recognition for the new LSI Logic Fibre Channel controller. Signed-off-by:
-
Michael Reed authored
Signed-off-by:
Michael Reed <mdr@sgi.com> Signed-off-by:
-
Jes Sorensen authored
Convert the SCSI transport class code to use a mutex rather than a semaphore. Signed-off-by:
Ingo Molnar <mingo@elte.hu> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
-
James Bottomley authored
There was a use before initialisation of c->name Signed-off-by: -
Christoph Hellwig authored
Convert kmalloc + memset to kzalloc or kcalloc in fusion. Signed-off-by:
-
Christoph Hellwig authored
Signed-off-by:
-
Christoph Hellwig authored
Adds hotplug support for SAS end devices. Unfortunately the fusion firmware doesn't generate similar events for expanders addition/removal so we can't support them yet. Eric has an idea about a clever scheme to find out about expander changes so that'll be added later on. Signed-off-by:
-
Salyzyn, Mark authored
The problem in dpt_i2o could be the pci config space accesses it triggers as it loads, dangerous to do if there is any I/O activity going on in the other driver (probable if a boot driver I guess). I approve this patch to dpt_i2o.c, and am applying it to the Adaptec branch of the driver. Thanks for the investigation Ryoji. --- In linux 2.6.15, data transfer does hang when both dpt_i2o and i2o_block drivers are loaded. It seems that location of pci_request_regions() are wrong. I moved it just behind pci_enable_device() like other drivers, and it becomes fine. Signed-off-by:
Ryoji Kamei <kamei@miraclelinux.com> Signed-off-by:
-
Jack Hammer authored
To avoid the "sda: got wrong page" message, the ServeRAID driver should be setting flags indicating that the Mode Sense commands are not supported. Signed-off-by:
Jack Hammer <jack_hammer@adaptec.com> Signed-off-by:
-
Andreas Herrmann authored
Replaced zfcp adapter attributes with fc_host attributes: fc_topology by port_type, physical_wwpn by permanent_port_name. Make use of fc_host attribute supported_speeds. Removed zfcp adapter attribute physical_s_id. Signed-off-by:
Andreas Herrmann <aherrman@de.ibm.com> Signed-off-by:
-
