On Wed, Mar 28, 2007 at 02:54:32PM -0700, Judith Lebzelter wrote:
> Hello,
>
> I have been running a series of kexec tests using LKDTT on the
> aacraid driver on this card (ASR-4805SAS (Marauder-E)) on x86_64
> using the latest top of scsi-misc git-tree(as of yesterday), and
> I have found that
Jeff Garzik wrote:
AN is a generic concept that I feel will propagate elsewhere.
I think SCSI already has it or am I imagining things again? :-)
Though perhaps it should be in a 'capability_flags' file rather than a
'media_change_event' file.
IMHO, if it's genhd.capability_flags then the f
Tejun Heo wrote:
Jeff Garzik wrote:
Kristen Carlson Accardi wrote:
Allow user space to determine if an ATAPI device supports
async notification (AN) of media changes. This is done by
adding a new sysfs file "async_notification" to genhd.
If the file reads 1, then the device supports async noti
Jeff Garzik wrote:
Kristen Carlson Accardi wrote:
Allow user space to determine if an ATAPI device supports
async notification (AN) of media changes. This is done by
adding a new sysfs file "async_notification" to genhd.
If the file reads 1, then the device supports async notification. If
the
Kristen Carlson Accardi wrote:
Allow user space to determine if an ATAPI device supports
async notification (AN) of media changes. This is done by
adding a new sysfs file "async_notification" to genhd.
If the file reads 1, then the device supports async
notification. If the file reads 0, it do
eh_timed_out call back (megasas_reset_timer) is used to throttle io to the
adapter
when it is called the first time for a scmd.
The MEGASAS_FW_BUSY flag is set and can_queue reduced to 16. The can_queue is
restored
from completion routine in following two conditions : 5 seconds has elapsed and
Hello,
I have been running a series of kexec tests using LKDTT on the
aacraid driver on this card (ASR-4805SAS (Marauder-E)) on x86_64
using the latest top of scsi-misc git-tree(as of yesterday), and
I have found that it is not coming up consistantly when booted
through kexec.
I have included
On Wed, 28 Mar 2007 12:47:04 -0500 Robert Jennings wrote:
> Adding a slave_configure function for the driver. Now the disks can be
> restarted by the scsi mid-layer when the are disconnected and reconnected.
>
> Signed-off-by: "Robert Jennings" <[EMAIL PROTECTED]>
> Signed-off-by: "Santiago Leon"
Adding a slave_configure function for the driver. Now the disks can be
restarted by the scsi mid-layer when the are disconnected and reconnected.
Signed-off-by: "Robert Jennings" <[EMAIL PROTECTED]>
Signed-off-by: "Santiago Leon" <[EMAIL PROTECTED]>
---
drivers/scsi/ibmvscsi/ibmvscsi.c | 18 ++
The request limit calculations used previously on the client failed to
mirror the state of the server. Additionally, when a value < 3 was provided
there could be problems setting can_queue and handling abort and reset
commands.
Signed-off-by: "Robert Jennings" <[EMAIL PROTECTED]>
Signed-off-by:
The Adapter build date that is to be printed on instantiation was not
displayed as a result of the supplemental adapter information structure
not being in sync with the Firmware; the driver took an early test cycle
version that had a miss-sized padded region at the head and the
structure was not re
James,
Resending these patches for inclusion in your tree.
There are two fixes for the ibmvscsi client driver in this set.
- Dynamic request_limit
The request_limit for the driver was not properly reflecting the value on
the server side and could cause can_queue to be set to improper values (-1)
On 3/28/07, Arjan van de Ven <[EMAIL PROTECTED]> wrote:
On Tue, 2007-03-27 at 09:17 -0700, Allexio Ju wrote:
> I thought those macros simply tell compiler to layout code in such a
> way that minimizes unnecessary jumps.
it's more than that. it generally also tells the processor what the
branch wi
On Wed, 28 Mar 2007, Bernhard Walle wrote:
> [PATCH] [qla2xxx] Remove duplicate pci_disable_device() call
>
> On the path qla2x00_probe_one() -> probe_failed -> qla2x00_free_device(),
> pci_disable_device() is executed twice, once in qla2x00_free_device()
> and once in qla2x00_probe_one().
>
> T
Just sweeping the floor clean in one spot. Some of these constants have
never been used in the driver or in the firmware (and thus are
meaningless). Triggered this patch because I discovered one of the
unused constants was actually incorrect and figured it was better to
clean them out than correct
On Tue, 2007-03-27 at 09:17 -0700, Allexio Ju wrote:
> On Thu, 2007-03-22 at 2007 2:24 AM, Arjan van de Ven wrote:
> > (I assume you're aware that likely/unlikely should only be
> > used for 99:1 or higher ratios, this one looks correct for sure)
> Could you share details of reasons why those macro
On Mon, Mar 26 2007, Mark Lobo wrote:
> Hello!
>
> I had a question about disabling the block layer for SCSI devices. We
> have an embedded device, and it runs 2.4.30. We need to be able to
> support a lot of SCSI devices (in the thousands) for our device, and we
> talk to the devices via SG. We a
On Tue, Mar 20 2007, FUJITA Tomonori wrote:
> bsg uses scsi_cmd_ioctl() for some SCSI/sg ioctl
> commands. scsi_cmd_ioctl() gets a request queue from a gendisk
> arguement. This prevents bsg being bound to SCSI devices that don't
> have a gendisk (like OSD). This adds a request_queue argument to
>
From: Christof Schmitt <[EMAIL PROTECTED]>
Correctly initialize the timer for FSF requests with jiffies + timeout.
Cc: Swen Schillig <[EMAIL PROTECTED]>
Acked-by: Heiko Carstens <[EMAIL PROTECTED]>
Signed-off-by: Christof Schmitt <[EMAIL PROTECTED]>
---
Please consider this patch for 2.6.21.
d
On Thu, Mar 22 2007, FUJITA Tomonori wrote:
> This patch addresses on two issues on bsg device allocation.
>
> - the current maxium number of bsg devices is 256. It's too small if
> we allocate bsg devices to all SCSI devices, transport entities, etc.
> This increses the maxium number to 32768 (ta
20 matches
Mail list logo
