Re: how to handle QUEUE_FULL/SAM_STAT_TASK_SET_FULL in userspace?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Chris Friesen wrote:

We recently moved from 2.6.10 to 2.6.14 and now we're seeing occasional QUEUE_FULL/SAM_STAT_TASK_SET_FULL errors being returned to userspace. These didn't ever show up in 2.6.10.

I found something that might be interesting.

With the the 3.01.18 fusion driver the queue length (as shown by "/sys/class/scsi_generic/sgX/device/queue_depth") was set to 7, while with the 3.02.57 fusion driver it was set to either 64 or 32.

It may be coincidence, but it's interesting that MPT_SCSI_CMD_PER_DEV_LOW is set to 7 in the earlier driver, and 32 in the later one, while MPT_SCSI_CMD_PER_DEV_HIGH went from 31 to 64.

Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux