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

2014-01-22 Thread Sha Zhengju
From: Sha Zhengju handai@taobao.com 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,

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

2014-01-22 Thread Sha Zhengju
From: Sha Zhengju handai@taobao.com 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.

RE: [PATCH] bfa: set correct command return code

2014-01-22 Thread Vijaya Mohan Guvva
-Original Message- From: Hannes Reinecke [mailto:h...@suse.de] Sent: Tuesday, January 14, 2014 2:56 PM To: James Bottomley Cc: linux-scsi@vger.kernel.org; Vijaya Mohan Guvva; Hannes Reinecke Subject: [PATCH] bfa: set correct command return code For various error conditions the bfa

RE: [PATCH 3.12 033/118] usb: xhci: Link TRB must not occur within a USB payload burst [NEW HARDWARE]

2014-01-22 Thread David Laight
From: walt On 01/21/2014 01:51 AM, David Laight wrote: From: Sarah Sharp On Mon, Jan 20, 2014 at 11:21:14AM +, David Laight wrote: ... A guess... In queue_bulk_sg_tx() try calling xhci_v1_0_td_remainder() instead of xhci_td_remainder(). David, I tried the one-liner below,

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread Mel Gorman
On Tue, Jan 21, 2014 at 10:04:29PM -0500, Ric Wheeler wrote: One topic that has been lurking forever at the edges is the current 4k limitation for file system block sizes. Some devices in production today and others coming soon have larger sectors and it would be interesting to see if it is

[Bug 69201] New: qla2xxx: Low-latency storage triggers lock contention

2014-01-22 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=69201 Bug ID: 69201 Summary: qla2xxx: Low-latency storage triggers lock contention Product: SCSI Drivers Version: 2.5 Kernel Version: 3.12.7 Hardware: All OS: Linux

[Bug 69201] qla2xxx: Low-latency storage triggers lock contention

2014-01-22 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=69201 --- Comment #1 from Bart Van Assche bvanass...@acm.org --- Created attachment 123011 -- https://bugzilla.kernel.org/attachment.cgi?id=123011action=edit perf report --stdio output -- You are receiving this mail because: You are watching the

Re: linux rdma 3.14 merge plans

2014-01-22 Thread Sagi Grimberg
On 1/22/2014 2:43 AM, Roland Dreier wrote: On Tue, Jan 21, 2014 at 2:00 PM, Or Gerlitz or.gerl...@gmail.com wrote: Roland, ping! the signature patches were posted three months ago. We deserve a response from the maintainer that goes beyond I need to think on that. Responsiveness was stated by

Re: [PATCH-v2 10/17] target: Add protection SGLs to target_submit_cmd_map_sgls

2014-01-22 Thread Sagi Grimberg
On 1/22/2014 12:17 AM, Nicholas A. Bellinger wrote: On Sun, 2014-01-19 at 14:12 +0200, Sagi Grimberg wrote: On 1/19/2014 4:44 AM, Nicholas A. Bellinger wrote: From: Nicholas Bellinger n...@linux-iscsi.org This patch adds support to target_submit_cmd_map_sgls() for accepting 'sgl_prot' +

Re: [PATCH-v2 11/17] target/iblock: Add blk_integrity + BIP passthrough support

2014-01-22 Thread Sagi Grimberg
On 1/22/2014 3:52 AM, Martin K. Petersen wrote: Sagi == Sagi Grimberg sa...@dev.mellanox.co.il writes: Sagi Please remind me why we ignore IP-CSUM guard type again? MKP, Sagi will this be irrelevant for the initiator as well? if so, I don't Sagi see a reason to expose this in RDMA verbs. I

Re: [PATCH-v2 12/17] target/file: Add DIF protection init/format support

2014-01-22 Thread Sagi Grimberg
On 1/22/2014 12:28 AM, Nicholas A. Bellinger wrote: On Sun, 2014-01-19 at 14:31 +0200, Sagi Grimberg wrote: On 1/19/2014 4:44 AM, Nicholas A. Bellinger wrote: From: Nicholas Bellinger n...@linux-iscsi.org This patch adds support for DIF protection init/format support into the FILEIO backend.

Hello

2014-01-22 Thread lisa
Could I have 5mins of your time to discuss a life changingmatter with you? -- To unsubscribe from this list: send the line unsubscribe linux-scsi in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread Ric Wheeler
On 01/22/2014 04:34 AM, Mel Gorman wrote: On Tue, Jan 21, 2014 at 10:04:29PM -0500, Ric Wheeler wrote: One topic that has been lurking forever at the edges is the current 4k limitation for file system block sizes. Some devices in production today and others coming soon have larger sectors and

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread Mel Gorman
On Wed, Jan 22, 2014 at 09:10:48AM -0500, Ric Wheeler wrote: On 01/22/2014 04:34 AM, Mel Gorman wrote: On Tue, Jan 21, 2014 at 10:04:29PM -0500, Ric Wheeler wrote: One topic that has been lurking forever at the edges is the current 4k limitation for file system block sizes. Some devices in

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread Ric Wheeler
On 01/22/2014 09:34 AM, Mel Gorman wrote: On Wed, Jan 22, 2014 at 09:10:48AM -0500, Ric Wheeler wrote: On 01/22/2014 04:34 AM, Mel Gorman wrote: On Tue, Jan 21, 2014 at 10:04:29PM -0500, Ric Wheeler wrote: One topic that has been lurking forever at the edges is the current 4k limitation for

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread Chris Mason
On Wed, 2014-01-22 at 09:34 +, Mel Gorman wrote: On Tue, Jan 21, 2014 at 10:04:29PM -0500, Ric Wheeler wrote: One topic that has been lurking forever at the edges is the current 4k limitation for file system block sizes. Some devices in production today and others coming soon have

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread Mel Gorman
On Wed, Jan 22, 2014 at 09:58:46AM -0500, Ric Wheeler wrote: On 01/22/2014 09:34 AM, Mel Gorman wrote: On Wed, Jan 22, 2014 at 09:10:48AM -0500, Ric Wheeler wrote: On 01/22/2014 04:34 AM, Mel Gorman wrote: On Tue, Jan 21, 2014 at 10:04:29PM -0500, Ric Wheeler wrote: One topic that has been

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread James Bottomley
On Tue, 2014-01-21 at 22:04 -0500, Ric Wheeler wrote: One topic that has been lurking forever at the edges is the current 4k limitation for file system block sizes. Some devices in production today and others coming soon have larger sectors and it would be interesting to see if it is time

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread James Bottomley
On Wed, 2014-01-22 at 15:14 +, Chris Mason wrote: On Wed, 2014-01-22 at 09:34 +, Mel Gorman wrote: On Tue, Jan 21, 2014 at 10:04:29PM -0500, Ric Wheeler wrote: One topic that has been lurking forever at the edges is the current 4k limitation for file system block sizes. Some

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread Ric Wheeler
On 01/22/2014 11:03 AM, James Bottomley wrote: On Wed, 2014-01-22 at 15:14 +, Chris Mason wrote: On Wed, 2014-01-22 at 09:34 +, Mel Gorman wrote: On Tue, Jan 21, 2014 at 10:04:29PM -0500, Ric Wheeler wrote: One topic that has been lurking forever at the edges is the current 4k

Re: [PATCH-v2 02/17] target: Add DIF CHECK_CONDITION ASC/ASCQ exception cases

2014-01-22 Thread Sagi Grimberg
On 1/19/2014 4:44 AM, Nicholas A. Bellinger wrote: From: Nicholas Bellinger n...@linux-iscsi.org This patch adds support for DIF related CHECK_CONDITION ASC/ASCQ exception cases into transport_send_check_condition_and_sense(). This includes: LOGICAL BLOCK GUARD CHECK FAILED LOGICAL

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread Chris Mason
On Wed, 2014-01-22 at 15:19 +, Mel Gorman wrote: On Wed, Jan 22, 2014 at 09:58:46AM -0500, Ric Wheeler wrote: On 01/22/2014 09:34 AM, Mel Gorman wrote: On Wed, Jan 22, 2014 at 09:10:48AM -0500, Ric Wheeler wrote: On 01/22/2014 04:34 AM, Mel Gorman wrote: On Tue, Jan 21, 2014 at

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread James Bottomley
On Wed, 2014-01-22 at 11:45 -0500, Ric Wheeler wrote: On 01/22/2014 11:03 AM, James Bottomley wrote: On Wed, 2014-01-22 at 15:14 +, Chris Mason wrote: On Wed, 2014-01-22 at 09:34 +, Mel Gorman wrote: On Tue, Jan 21, 2014 at 10:04:29PM -0500, Ric Wheeler wrote: One topic that has

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread James Bottomley
On Wed, 2014-01-22 at 17:02 +, Chris Mason wrote: On Wed, 2014-01-22 at 15:19 +, Mel Gorman wrote: On Wed, Jan 22, 2014 at 09:58:46AM -0500, Ric Wheeler wrote: On 01/22/2014 09:34 AM, Mel Gorman wrote: On Wed, Jan 22, 2014 at 09:10:48AM -0500, Ric Wheeler wrote: On 01/22/2014

Re: [PATCH-v2 03/17] target/sbc: Add DIF setup in sbc_check_prot + sbc_parse_cdb

2014-01-22 Thread Sagi Grimberg
On 1/22/2014 12:48 AM, Nicholas A. Bellinger wrote: + cmd-prot_handover = PROT_SEPERATED; I know that we are not planning to support interleaved mode at the moment, But I think that the protection handover type is the backstore preference and should be taken from se_dev. But it is not

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread Chris Mason
On Wed, 2014-01-22 at 09:21 -0800, James Bottomley wrote: On Wed, 2014-01-22 at 17:02 +, Chris Mason wrote: [ I like big sectors and I cannot lie ] I really think that if we want to make progress on this one, we need code and someone that owns it. Nick's work was impressive, but it

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread James Bottomley
On Wed, 2014-01-22 at 18:02 +, Chris Mason wrote: On Wed, 2014-01-22 at 09:21 -0800, James Bottomley wrote: On Wed, 2014-01-22 at 17:02 +, Chris Mason wrote: [ I like big sectors and I cannot lie ] I think I might be sceptical, but I don't think that's showing in my concerns ...

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread Ric Wheeler
On 01/22/2014 01:13 PM, James Bottomley wrote: On Wed, 2014-01-22 at 18:02 +, Chris Mason wrote: On Wed, 2014-01-22 at 09:21 -0800, James Bottomley wrote: On Wed, 2014-01-22 at 17:02 +, Chris Mason wrote: [ I like big sectors and I cannot lie ] I think I might be sceptical, but I

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread James Bottomley
On Wed, 2014-01-22 at 13:17 -0500, Ric Wheeler wrote: On 01/22/2014 01:13 PM, James Bottomley wrote: On Wed, 2014-01-22 at 18:02 +, Chris Mason wrote: On Wed, 2014-01-22 at 09:21 -0800, James Bottomley wrote: On Wed, 2014-01-22 at 17:02 +, Chris Mason wrote: [ I like big sectors

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread Chris Mason
On Wed, 2014-01-22 at 10:13 -0800, James Bottomley wrote: On Wed, 2014-01-22 at 18:02 +, Chris Mason wrote: We're likely to have people mixing 4K drives and fill in some other size here on the same box. We could just go with the biggest size and use the existing bh code for the

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread Ric Wheeler
On 01/22/2014 01:35 PM, James Bottomley wrote: On Wed, 2014-01-22 at 13:17 -0500, Ric Wheeler wrote: On 01/22/2014 01:13 PM, James Bottomley wrote: On Wed, 2014-01-22 at 18:02 +, Chris Mason wrote: On Wed, 2014-01-22 at 09:21 -0800, James Bottomley wrote: On Wed, 2014-01-22 at 17:02

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread James Bottomley
On Wed, 2014-01-22 at 18:37 +, Chris Mason wrote: On Wed, 2014-01-22 at 10:13 -0800, James Bottomley wrote: On Wed, 2014-01-22 at 18:02 +, Chris Mason wrote: [agreement cut because it's boring for the reader] Realistically, if you look at what the I/O schedulers output on a standard

Re: [LSF/MM TOPIC] [ATTEND] scsi-mq

2014-01-22 Thread James Smart
James, I'd like to attend to participate in the EH, MQ, and T10 PI RDMA discussions. -- james s On 1/16/2014 11:29 AM, Sagi Grimberg wrote: On 1/16/2014 1:05 AM, Nicholas A. Bellinger wrote: Hi all, I'd like to discuss the current state of scsi-mq prototype code. And now that blk-mq

[LSF/MM ATTEND] EH, MQ, RDMA T10-PI

2014-01-22 Thread James Smart
Hello, I would like to attend LSF/MM 2014. I would like to continue discussions held on the eh enhancements, multi-queue, and addition of T10-PI to RDMA/iSER. I'm currently the maintainer of the Emulex lpfc driver and bring years of scsi, driver, firmware, and asic experience. thank

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread James Bottomley
On Wed, 2014-01-22 at 13:39 -0500, Ric Wheeler wrote: On 01/22/2014 01:35 PM, James Bottomley wrote: On Wed, 2014-01-22 at 13:17 -0500, Ric Wheeler wrote: [...] I think that the key to having the file system work with larger sectors is to create them properly aligned and use the actual,

project!!

2014-01-22 Thread Howard Maxim
I am Howard Maxim,retired professional broker.I have a project for you or your firm.My private email is project20...@gmail.com -- To unsubscribe from this list: send the line unsubscribe linux-scsi in the body of a message to majord...@vger.kernel.org More majordomo info at

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread Ric Wheeler
On 01/22/2014 01:37 PM, Chris Mason wrote: Circling back to what we might talk about at the conference, Ric do you have any ideas on when these drives might hit the wild? -chris I will poke at vendors to see if we can get someone to make a public statement, but I cannot do that for them. Ric

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread Andrew Morton
On Wed, 22 Jan 2014 11:30:19 -0800 James Bottomley james.bottom...@hansenpartnership.com wrote: But this, I think, is the fundamental point for debate. If we can pull alignment and other tricks to solve 99% of the problem is there a need for radical VM surgery? Is there anything coming down

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread Chris Mason
On Wed, 2014-01-22 at 11:50 -0800, Andrew Morton wrote: On Wed, 22 Jan 2014 11:30:19 -0800 James Bottomley james.bottom...@hansenpartnership.com wrote: But this, I think, is the fundamental point for debate. If we can pull alignment and other tricks to solve 99% of the problem is there a

Re: Persistent reservation behaviour/compliance with redundant controllers

2014-01-22 Thread Matthias Eble
2014/1/7 James Bottomley james.bottom...@hansenpartnership.com On Mon, 2014-01-06 at 23:53 +0100, Matthias Eble wrote: 2014/1/6 Lee Duncan ldun...@suse.com: On 12/25/2013 03:00 PM, Matthias Eble wrote: Here's the dmmp map 360002aca6e6b dm-6 3PARdata,VV size=2.0T

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread Martin K. Petersen
Ric == Ric Wheeler rwhee...@redhat.com writes: Ric I will have to see if I can get a storage vendor to make a public Ric statement, but there are vendors hoping to see this land in Linux Ric in the next few years. I assume that anyone with a shipping device Ric will have to at least emulate the

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread Martin K. Petersen
James == James Bottomley james.bottom...@hansenpartnership.com writes: or even (not today, but some day) reject the IO. James I really doubt this. All 4k drives today do RMW ... I don't see James that changing any time soon. All consumer grade 4K phys drives do RMW. It's a different story

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread Jan Kara
On Wed 22-01-14 09:00:33, James Bottomley wrote: On Wed, 2014-01-22 at 11:45 -0500, Ric Wheeler wrote: On 01/22/2014 11:03 AM, James Bottomley wrote: On Wed, 2014-01-22 at 15:14 +, Chris Mason wrote: On Wed, 2014-01-22 at 09:34 +, Mel Gorman wrote: On Tue, Jan 21, 2014 at

Re: [usb-storage] Re: usb disk recognized but fails

2014-01-22 Thread Milan Svoboda
8801fdbb2c00 2290129737 S Bo:3:004:2 -115 31 = 55534243 5f00 0010 8a28 004a856e af08 00 8801fdbb2c00 2290129782 C Bo:3:004:2 0 31 8800d4a51b40 2290129803 S Bi:3:004:1 -115 4096 8800d4a51b40 2301288990 C Bi:3:004:1 -32 512 =

[Bug 60758] module scsi_wait_scan not found kernel panic on boot

2014-01-22 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=60758 --- Comment #54 from Akemi Yagi tora...@elrepo.org --- (In reply to Lin Feng from comment #53) though it's somthing about virtio driver(my guest uses virtio as the storage driver), looking into this commit it is mainly about C code changes, not

Re: [usb-storage] Re: usb disk recognized but fails

2014-01-22 Thread Alan Stern
On Wed, 22 Jan 2014, Milan Svoboda wrote: This continued a few more times until the computer gave up. Maybe there is something wrong with one particular block at that address on the disk. I tried to run fdisk /dev/sdb which obivously failed but it tried to access sectors 0, 1, 2, 3 which

Re: [PATCH-v2 12/17] target/file: Add DIF protection init/format support

2014-01-22 Thread Nicholas A. Bellinger
On Wed, 2014-01-22 at 12:12 +0200, Sagi Grimberg wrote: On 1/22/2014 12:28 AM, Nicholas A. Bellinger wrote: On Sun, 2014-01-19 at 14:31 +0200, Sagi Grimberg wrote: On 1/19/2014 4:44 AM, Nicholas A. Bellinger wrote: From: Nicholas Bellinger n...@linux-iscsi.org This patch adds support

Re: [PATCH-v2 02/17] target: Add DIF CHECK_CONDITION ASC/ASCQ exception cases

2014-01-22 Thread Nicholas A. Bellinger
On Wed, 2014-01-22 at 18:44 +0200, Sagi Grimberg wrote: On 1/19/2014 4:44 AM, Nicholas A. Bellinger wrote: From: Nicholas Bellinger n...@linux-iscsi.org This patch adds support for DIF related CHECK_CONDITION ASC/ASCQ exception cases into transport_send_check_condition_and_sense().

Re: [PATCH-v2 03/17] target/sbc: Add DIF setup in sbc_check_prot + sbc_parse_cdb

2014-01-22 Thread Nicholas A. Bellinger
On Wed, 2014-01-22 at 20:00 +0200, Sagi Grimberg wrote: On 1/22/2014 12:48 AM, Nicholas A. Bellinger wrote: + cmd-prot_handover = PROT_SEPERATED; I know that we are not planning to support interleaved mode at the moment, But I think that the protection handover type is the backstore

Re: [LSF/MM ATTEND] interest in blk-mq, scsi-mq, dm-cache, dm-thinp, dm-*

2014-01-22 Thread Giridhar Malavali
On 1/22/14 1:54 AM, Bart Van Assche bvanass...@acm.org wrote: On 01/16/14 23:35, Giridhar Malavali wrote: On 1/10/14 10:27 AM, Mike Snitzer snit...@redhat.com wrote: I would like to attend to participate in discussions related to topics listed in the subject. As a maintainer of DM I'd be

[LSF/MM ATTEND] Interested in bk-mq, scsi-mq , ISER, T10PI

2014-01-22 Thread Jayamohan Kallickal
James, I'd like to attend LSF/MM 2014. Have been trying out blk-mq / scsi-mq on Emulex offloaded iSCSi Solution. Also interested in T10 PI, iSER and RDMA. Also, am the Maintainer of be2iscsi driver. Thanks Jay -- To unsubscribe from this list: send the line unsubscribe linux-scsi in the

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread David Lang
On Wed, 22 Jan 2014, Chris Mason wrote: On Wed, 2014-01-22 at 11:50 -0800, Andrew Morton wrote: On Wed, 22 Jan 2014 11:30:19 -0800 James Bottomley james.bottom...@hansenpartnership.com wrote: But this, I think, is the fundamental point for debate. If we can pull alignment and other tricks

Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes

2014-01-22 Thread Theodore Ts'o
On Wed, Jan 22, 2014 at 06:46:11PM -0800, David Lang wrote: It's extremely unlikely that drive manufacturers will produce drives that won't work with any existing OS, so they are going to support smaller writes in firmware. If they don't, they won't be able to sell their drives to anyone