diff options
| author | Salyzyn, Mark <mark_salyzyn@adaptec.com> | 2007-07-27 09:48:49 -0400 |
|---|---|---|
| committer | James Bottomley <jejb@mulgrave.localdomain> | 2007-07-28 10:09:07 -0400 |
| commit | b90f90d2303f27b9b241ab78419a07b41de5ac62 (patch) | |
| tree | fe609680bf9030fdebe38928dc05ca9d0f553590 /net | |
| parent | 80b1c7bdc1cc69a804f416761f5faafcb6284086 (diff) | |
| download | linux-3.10-b90f90d2303f27b9b241ab78419a07b41de5ac62.tar.gz linux-3.10-b90f90d2303f27b9b241ab78419a07b41de5ac62.tar.bz2 linux-3.10-b90f90d2303f27b9b241ab78419a07b41de5ac62.zip | |
[SCSI] aacraid: add SCSI SYNCHONIZE_CACHE range checking
Customer running an application that issues SYNCHRONIZE_CACHE calls
directly noticed the broad stroke of the current implementation in the
aacraid driver resulting in multiple applications feeding I/O to the
storage causing the issuing application to stall for long periods of
time. By only waiting for the current WRITE commands, rather than all
commands, to complete; and those that are in range of the
SYNCHRONIZE_CACHE call that would associate more tightly with the
issuing application before telling the Firmware to flush it's dirty
cache, we managed to reduce the stalling. The Firmware itself still
flushes all the dirty cache associated with the array ignoring the
range, it just does so in a more timely manner.
Signed-off-by: Mark Salyzyn <aacraid@adaptec.com>
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions