[PATCH] scsi-sd: removed unused SD_PASSTHROUGH_RETRIES

2014-01-23 Thread Sha Zhengju
From: Sha Zhengju Signed-off-by: Sha Zhengju --- drivers/scsi/sd.h |1 - 1 file changed, 1 deletion(-) diff --git a/drivers/scsi/sd.h b/drivers/scsi/sd.h index 26895ff..3bbe4df 100644 --- a/drivers/scsi/sd.h +++ b/drivers/scsi/sd.h @@ -24,7 +24,6 @@ * Number of allowed retries

[PATCH 2/2] scsi_scan: introduce a new variable to represent INQUIRY VERSION field

2014-01-22 Thread Sha Zhengju
From: Sha Zhengju As per Doug Gilbert's suggestion, introduce a new variable to represent the resp[2] of standard INQUIRY data. For different scsi devices, the linux scsi_level is computed based on the resp[2] value. This will make the code more easier to understand. Signed-off-by: Sha Zh

[PATCH V2 1/2] scsi_debug: unify scsi_level in proc and sysfs

2014-01-22 Thread Sha Zhengju
From: Sha Zhengju There're severel interfaces to show scsi_level value of scsi_debug, but they're not in consistent, e.g.: 1) #cat /sys/bus/pseudo/drivers/scsi_debug/scsi_level 5 2) #cat /proc/scsi/scsi_debug/7 scsi_debug adapter driver, version 1.82 [20100324] num_tgts=1, shared

Re: [PATCH] scsi_debug: unify scsi_level in proc and sysfs

2014-01-21 Thread Sha Zhengju
On Tue, Jan 21, 2014 at 11:07 PM, Douglas Gilbert wrote: > On 14-01-21 04:52 AM, Sha Zhengju wrote: >> >> From: Sha Zhengju >> >> There're severel interfaces to show scsi_level value of scsi_debug, >> but they're not in consistent. E.g: >>

[PATCH] scsi_debug: unify scsi_level in proc and sysfs

2014-01-21 Thread Sha Zhengju
From: Sha Zhengju There're severel interfaces to show scsi_level value of scsi_debug, but they're not in consistent. E.g: 1) #cat /sys/bus/pseudo/drivers/scsi_debug/scsi_level 5 2) #cat /proc/scsi/scsi_debug/7 scsi_debug adapter driver, version 1.82 [20100324] num_tgts=1, shared

[LSF/MM ATTEND] Persistent memory, per-bdi cgroup, scsi

2014-01-15 Thread Sha Zhengju
Hello, I'd like to attend LSF/MM 2014. Whether expose persitent memory directly to the CPU or hide it behind a PCIe IO controller, I'm interested to learn/discuss the short and long term mechanisms that exploiting its benefits of fast, bytes-addressable, non-volatile. Last year I mainly worked on