The original behavior was to refuse all pages after the maximum number of
segments has been reached. However, some drivers (like st) craft their buffers
to potentially require exactly max segments and multiple pages in the last
segment. This patch modifies the check to allow pages that can be
On Wed, Feb 20, 2013 at 10:43:50AM -0500, Alan Stern wrote:
On Wed, 20 Feb 2013, Aaron Lu wrote:
In August 2010, Jens and Alan discussed about Runtime PM and the block
layer. http://marc.info/?t=12825910841r=1w=2
And then Alan has given a detailed implementation guide:
Hi Eddie,
On Tue, 2013-02-19 at 18:30 -0800, Eddie Wai wrote:
The code seems correct as it make sense to impose the same hardware
segment boundary limit on both the blk queue and the DMA code. It would
be an easy alternative to simply prevent the shost-dma_boundary from
being set to
I'm sorry, I forgot to mention hardware details. It isn't aacraid, it
is megaraid-based Dell PERC H700 w/ 1GB NVRAM and 12x 450GB 15k SAS
drives in RAID-10. All in Dell R510 server.
Thanks,
Martin
Dne 20.2.2013 21:48, Nicholas A. Bellinger napsal(a):
Hi Martin,
CC'ing linux-scsi here, as
GFP_KERNEL may cause pci_pool_alloc() sleep,
so we need use GFP_ATOMIC instead of GFP_KERNEL.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Denis Efremov yefremov.de...@gmail.com
---
drivers/scsi/megaraid/megaraid_mm.c | 2 +-
1 file changed, 1 insertion(+), 1
Regarding changes like this:
- printk(MYIOC_s_NOTE_FMT [%d:%d:%d:%d]
+ printk(MYIOC_s_NOTE_FMT [%d:%d:%d:%llu]
FCP_ResponseInfo=%08xh\n, ioc-name,
sc-device-host-host_no, sc-device-channel,
On Thu, 2013-02-21 at 16:15 +, Elliott, Robert (Server Storage)
wrote:
Regarding changes like this:
- printk(MYIOC_s_NOTE_FMT [%d:%d:%d:%d]
+ printk(MYIOC_s_NOTE_FMT [%d:%d:%d:%llu]
FCP_ResponseInfo=%08xh\n, ioc-name,
This patch set (two of the patches are being resent) fixes and enhances
the functionality of the Hyper-V storage driver
K. Y. Srinivasan (3):
Drivers: scsi: storvsc: Initialize the sglist
Drivers: scsi: storvsc: Restructure error handling code on command
completion
Drivers: scsi:
In preparation for handling additional sense codes, restructure and cleanup
the error handling code in the command completion code path.
Signed-off-by: K. Y. Srinivasan k...@microsoft.com
Reviewed-by: Haiyang Zhang haiya...@microsoft.com
---
drivers/scsi/storvsc_drv.c | 101
Initialize sglist before using it.
Signed-off-by: K. Y. Srinivasan k...@microsoft.com
Cc: sta...@vger.kernel.org
---
drivers/scsi/storvsc_drv.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/scsi/storvsc_drv.c b/drivers/scsi/storvsc_drv.c
index 270b3cf..5ada1d0
Handle LUN size changes by re-scanning the device.
Signed-off-by: K. Y. Srinivasan k...@microsoft.com
Reviewed-by: Haiyang Zhang haiya...@microsoft.com
---
drivers/scsi/storvsc_drv.c | 31 +++
1 files changed, 31 insertions(+), 0 deletions(-)
diff --git
From: Olaf Hering o...@aepfle.de
Set scsi_device-no_write_same because the host does not support it.
Also blacklist WRITE_SAME to avoid (and log) accident usage.
If the guest uses the ext4 filesystem, storvsc hangs while it prints
these messages in an endless loop:
...
[ 161.459523] hv_storvsc
I highly doubt hot-insert and hot-remove of HDDs from the 4-bay
container (without removing the corresponding USB/eSATA adaptor) will
work.
The USB/eSATA adaptor does not have a way to inform the host that the
eSATA side has been disconnected from the HDD. That functionality
isn't in the
On 13-02-21 02:26 PM, Sarah Sharp wrote:
Cc-ing the SCSI and USB storage list.
Folks, does the attached picture look like a sane setup? I've never
used mini-SaS to eSATA adapter before, let alone with four eSATA to USB
3.0 adapters.
Well SAS to eSATA is okay (works for me: LSI SAS9212-4i4e
Hi Martin,
On Thu, 2013-02-21 at 12:43 +0100, Martin Svec wrote:
I'm sorry, I forgot to mention hardware details. It isn't aacraid, it
is megaraid-based Dell PERC H700 w/ 1GB NVRAM and 12x 450GB 15k SAS
drives in RAID-10. All in Dell R510 server.
Jan Engelhardt (CC'ed) mentioned the
On Thu, Feb 21, 2013 at 03:48:42PM -0500, Douglas Gilbert wrote:
On 13-02-21 02:26 PM, Sarah Sharp wrote:
Cc-ing the SCSI and USB storage list.
Folks, does the attached picture look like a sane setup? I've never
used mini-SaS to eSATA adapter before, let alone with four eSATA to USB
3.0
On Thu, Feb 21, 2013 at 05:27:00PM -0300, Fabio David wrote:
On Thu, Feb 21, 2013 at 4:26 PM, Sarah Sharp sarah.a.sh...@linux.intel.com
wrote:
On Tue, Jan 29, 2013 at 12:56:02PM -0200, Fabio David wrote:
Do you have any suggestions?
A couple possible root causes come to mind:
1.
First forgive me for using outlook for this, if there are any issues with what
I sent let me know and I'll send it again from gmail. This is also my first
attempt at a kernel patch so please be gentle.
This patch was written to enable tape statistics via sysfs for the dt driver
based on kernel
18 matches
Mail list logo
