On 06/18/14 05:44, Jens Axboe wrote:
> Thanks for posting these numbers, Bart. The CPU utilization and IOPS
> speak a very clear message. The only mystery is why the singe threaded
> performance is down. That we need to get sort, but it's not a show
> stopper for inclusion.
>
> If you run the sing
Once calling scsi_host_put, be careful to not access qla_hw_data through
the Scsi_Host private data (ie, scsi_qla_host base_vha).
Signed-off-by: Joe Lawrence
---
drivers/scsi/qla2xxx/qla_os.c |6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/scsi/qla2xxx/qla_os
There are various callers of qla2x00_check_reg{32,16}_for_disconnect
that may schedule board removal on PCI-disconnect. Test-and-set a
dedicated flag before scheduling board_disable so it is invoked only
once.
Signed-off-by: Joe Lawrence
---
drivers/scsi/qla2xxx/qla_def.h |3 +++
drivers/sc
Hi Chad, Giri, et al.
Stratus has been testing the upstream qla2xxx driver against surprise
device removal and has found a few minor issues along the way. With
this patchset, results have been good. Although the following changes
may be most interesting on a Stratus platform, they should be appl
Take advantage of commit fe1b806f "qla2xxx: Refactor shutdown code so
some functionality can be reused" to remove an inlined copy of
qla2x00_clear_drv_active in the driver's probe hardware error path.
Signed-off-by: Joe Lawrence
---
drivers/scsi/qla2xxx/qla_os.c | 13 +++--
1 file chan
Introduce mutual exclusion between the qla2xxx_remove_one PCI driver
callback and qla2x00_disable_board_on_pci_error, which is scheduled as
board_disable work by qla2x00_check_reg{32,16}_for_disconnect:
* Leave the driver-specific data attached to the underlying PCI device
intact in qla2x00_disabl
Add an uint16_t variant of qla2x00_check_reg_for_disconnect and use
these routines to check and schedule a PCI-disconnected board from a
centralized place.
Signed-off-by: Joe Lawrence
---
drivers/scsi/qla2xxx/qla_gbl.h |3 ++-
drivers/scsi/qla2xxx/qla_isr.c | 28 +--
The PCI register read checking introduced in commit f3ddac19 "qla2xxx:
Disable adapter when we encounter a PCI disconnect" is active during
driver probe. Hold off scheduling any board removal until the driver
probe has completed. This ensures that the the board_disable work
structure is initializ
Hi Joe,
Thanks for the patches. We will review and update.
-- Giri
On 6/18/14 7:02 AM, "Joe Lawrence" wrote:
>Hi Chad, Giri, et al.
>
>Stratus has been testing the upstream qla2xxx driver against surprise
>device removal and has found a few minor issues along the way. With
>this patchset, res
Hi friend. I want to transfer USD5.5Million into your account Contact
me for more details.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
https://bugzilla.kernel.org/show_bug.cgi?id=78281
Bug ID: 78281
Summary: aacraid: swiotlb buffer is full (sz: 255 bytes)
Product: SCSI Drivers
Version: 2.5
Kernel Version: 3.14-0.bpo.1-amd64 #1 SMP Debian 3.14.5-1~bpo70+1
(2014-0
https://bugzilla.kernel.org/show_bug.cgi?id=78281
--- Comment #1 from H. Wilmer ---
PS:
04:00.0 RAID bus controller: Adaptec AAC-RAID (Rocket) (rev 02)
Subsystem: IBM ServeRAID 8k/8k-l8
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+
Stepping- SERR+ FastB2B- D
> -Original Message-
> From: Jens Axboe [mailto:ax...@kernel.dk]
> Sent: Tuesday, 17 June, 2014 10:45 PM
> To: Bart Van Assche; Christoph Hellwig; James Bottomley
> Cc: Bart Van Assche; Elliott, Robert (Server Storage); linux-
> s...@vger.kernel.org; linux-ker...@vger.kernel.org
> Subject
Currently the scsi_debug driver wraps every queued command
with the host_lock and every mid-level completion callback
(apart from delay=0) with a spinlock.
Attached is a patch against Linus's tree that also applies
to lk 3.15.1 . It attempts to address some of these issues.
ChangeLog
- 'host_l
[ Copied. First sent to linux-hotplug ]
Hi,
I have a many identical looking USB drives in two btrfs multi-device
configurations. I was unplugging and replugging a few devices to
identify which physical device belonged to which btrfs filesystem.
Running "btrfs fi show" during this unplugging/replu
This patch adds an function to restart the port dma engine.
Signed-off-by: Loc Ho
Signed-off-by: Suman Tripathi
---
drivers/ata/ahci.h| 1 +
drivers/ata/libahci.c | 12
2 files changed, 13 insertions(+)
diff --git a/drivers/ata/ahci.h b/drivers/ata/ahci.h
index af63c75..3c176
Signed-off-by: Loc Ho
Signed-off-by: Suman Tripathi
---
Suman Tripathi (2):
libahci: Implement the function ahci_restart_engine to restart the
port dma engine.
ata: Fix the dma state machine lockup for the IDENTIFY DEVICE PIO mode
command.
drivers/ata/ahci.h | 2 ++
drivers/a
Signed-off-by: Loc Ho
Signed-off-by: Suman Tripathi
---
Suman Tripathi (2):
libahci: Implement the function ahci_restart_engine to restart the
port dma engine.
ata: Fix the dma state machine lockup for the IDENTIFY DEVICE PIO mode
command.
drivers/ata/ahci.h | 2 ++
drivers/a
This patch adds an function to restart the port dma engine.
Signed-off-by: Loc Ho
Signed-off-by: Suman Tripathi
---
drivers/ata/ahci.h| 1 +
drivers/ata/libahci.c | 12
2 files changed, 13 insertions(+)
diff --git a/drivers/ata/ahci.h b/drivers/ata/ahci.h
index af63c75..3c176
This patch fixes the dma state machine lockup due to the processing
of IDENTIFY DEVICE PIO mode command. The X-Gene AHCI controller
has an errata in which it cannot clear the BSY bit after
receiving the PIO setup FIS and results the dma state machine to go
into the CMFatalErrorUpdate state resultin
20 matches
Mail list logo
