linux-scsi mailing list

FromSubjectsort iconDate
Maksim Rayskiy
Re: [linux-pm] [RFC] Deferred disk spinup during system resume
Yes, asynchronous suspend/resume is enabled - it saves about 0.5 second in my case. But resume blocks anyway because disk driver is waiting on sd_resume() to complete. I am wondering if we could let the resume proceed while spinup is going on, just mark the scsi device as quiescent to block any data transfers. --
Dec 30, 5:49 pm 2010
Tejun Heo
Re: [linux-pm] [RFC] Deferred disk spinup during system resume
Yeah, it was asynchronous for a while when suspend/resume were implemented in libata proper. It's a bit trickier to do that with sd doing the higher level part. Hmmm... most SATA disks spin up automatically anyway so disabling START_STOP from sd should do the trick. Does the following achieve async resume? echo 0 > /sys/block/sdX/device/scsi_disk/h:c:i:l/manage_start_stop The problem is that the above would also prevent the kernel from issuing STANDBY_NOW on suspend or power down. ...
Dec 31, 4:27 am 2010
Tejun Heo
Re: [linux-pm] [RFC] Deferred disk spinup during system resume
So, something like the following. It's completely untested. Proceed with caution. diff --git a/drivers/ata/libata-eh.c b/drivers/ata/libata-eh.c index 17a6378..d8d2aa8 100644 --- a/drivers/ata/libata-eh.c +++ b/drivers/ata/libata-eh.c @@ -3252,6 +3252,48 @@ static int ata_eh_maybe_retry_flush(struct ata_device *dev) return rc; } +static int ata_eh_maybe_verify(struct ata_device *dev) +{ + struct ata_link *link = dev->link; + struct ata_taskfile tf; + unsigned int ...
Dec 31, 4:45 am 2010
michaelc
[PATCH 5/5] libiscsi: use bh locking instead of irq with ...
From: Mike Christie <michaelc@cs.wisc.edu> The session lock is taken in threads, timers, and bottom halves like softirqs and tasklets. All the code but iscsi_conn/session_failure take the session lock with the spin_lock_bh call. This was done because I thought some offload drivers would be calling these functions from a irq. They never did, so this patch has iscsi_conn/session_failure use the bh locking. Signed-off-by: Mike Christie <michaelc@cs.wisc.edu> --- drivers/scsi/libiscsi.c | ...
Dec 31, 1:22 am 2010
michaelc
[PATCH 2/5] be2iscsi: fix gfp use in alloc_pdu
From: Mike Christie <michaelc@cs.wisc.edu> The pdu allication callout is called from a spin lock and in the IO path so we cannot use GFP_KERNEL. This has the driver use GFP_ATOMIC. Signed-off-by: Mike Christie <michaelc@cs.wisc.edu> --- drivers/scsi/be2iscsi/be_main.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/scsi/be2iscsi/be_main.c b/drivers/scsi/be2iscsi/be_main.c index 75a85aa..be07ca0 100644 --- a/drivers/scsi/be2iscsi/be_main.c +++ ...
Dec 31, 1:22 am 2010
michaelc
[PATCH 3/5] be2iscsi: fix null ptr when accessing task hdr
From: Mike Christie <michaelc@cs.wisc.edu> If alloc_pdu fails then the task->hdr pointer may not be set. This adds a check for this case in the cleanup callback. Signed-off-by: Mike Christie <michaelc@cs.wisc.edu> --- drivers/scsi/be2iscsi/be_main.c | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/drivers/scsi/be2iscsi/be_main.c b/drivers/scsi/be2iscsi/be_main.c index be07ca0..79cefbe 100644 --- a/drivers/scsi/be2iscsi/be_main.c +++ ...
Dec 31, 1:22 am 2010
michaelc
iscsi changes for 2.6.38
These patches are for 2.6.38. They were made over scsi-rc-fixes. They fix a couple bugs and remove the host lock from the queuecommand path. [PATCH 1/5] libiscsi: add more informative failure message during iscsi scsi eh [PATCH 2/5] be2iscsi: fix gfp use in alloc_pdu [PATCH 3/5] be2iscsi: fix null ptr when accessing task hdr [PATCH 4/5] libiscsi: do not take host lock in queuecommand [PATCH 5/5] libiscsi: use bh locking instead of irq with session lock --
Dec 31, 1:22 am 2010
michaelc
[PATCH 4/5] libiscsi: do not take host lock in queuecommand
From: Mike Christie <michaelc@cs.wisc.edu> iscsi_tcp, ib_iser, cxgb*, be2iscsi and bnx2i do not use the host lock and do not take the session lock against a irq, so this patch drops the DEF_SCSI_QCMD use. Instead we just take the session lock and disable bhs. Signed-off-by: Mike Christie <michaelc@cs.wisc.edu> --- drivers/scsi/libiscsi.c | 37 ++++++++++++++----------------------- include/scsi/libiscsi.h | 3 ++- 2 files changed, 16 insertions(+), 24 deletions(-) diff --git ...
Dec 31, 1:22 am 2010
michaelc
[PATCH 1/5] libiscsi: add more informative failure messa ...
From: Mike Christie <michaelc@cs.wisc.edu> This adds a more informative error code and message for the iscsi scsi eh session drop paths. This allows you to distinguish if the session was dropped due to a connection failure vs the iscsi layer dropping the session due to scsi eh failure processing. Signed-off-by: Mike Christie <michaelc@cs.wisc.edu> --- drivers/scsi/libiscsi.c | 10 +++++----- include/scsi/iscsi_if.h | 1 + 2 files changed, 6 insertions(+), 5 deletions(-) diff --git ...
Dec 31, 1:22 am 2010
Matthew Wilcox
Re: Linux support for the LSI SAS8208ELP
http://marc.info/?l=linux-scsi&m=129019864003449&w=2 (ok, 0x55 vs 0x59, but dollars-to-doughnuts it's the same 'problem') -- Matthew Wilcox Intel Open Source Technology Centre "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." --
Dec 31, 10:52 am 2010
Christian Schmidt
Linux support for the LSI SAS8208ELP
Hi, I've recently bought a mainboard that's equipped with a device that is identified (by lspci) as LSI SAS8208ELP (Vendor ID 0x1000, Device ID 0x0059). It's not currently supported by the Linux kernel, but appears to be working with the mpt fusion sas driver. echo "0x1000 0x0059" >/sys/bus/pci/drivers/mptsas/new_id brings the chip online. It seems I'm not the only one with this chip, ...
Dec 31, 9:43 am 2010
Moore, Eric
RE: Linux support for the LSI SAS8208ELP
This has been asked for many times before. The deal is we don't support the MegaRAID software raid controllers with the mptsas driver. The firmware and BIOS that goes on the megaraid controllers is developed and tested by the MegaRAID team, and designed to work with the megasr driver. So if you were to add those device ids to mptsas mainstream drivers, our division of LSI is not going to be able to provide support those configurations; in other words, we have never validated those controllers ...
Dec 31, 11:53 am 2010
previous daytodaynext day
December 30, 2010December 31, 2010None