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 (ram) size=102
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 Zhengju
> -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
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 tri
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
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
https://bugzilla.kernel.org/show_bug.cgi?id=69201
--- Comment #1 from Bart Van Assche ---
Created attachment 123011
--> https://bugzilla.kernel.org/attachment.cgi?id=123011&action=edit
perf report --stdio output
--
You are receiving this mail because:
You are watching the assignee of the bug.
On 1/22/2014 2:43 AM, Roland Dreier wrote:
On Tue, Jan 21, 2014 at 2:00 PM, Or Gerlitz 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 Linus to be the #
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
This patch adds support to target_submit_cmd_map_sgls() for
accepting 'sgl_prot' + 'sgl_prot_count' parameter
On 1/22/2014 3:52 AM, Martin K. Petersen wrote:
"Sagi" == Sagi Grimberg 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 don't see much use for
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
This patch adds support for DIF protection init/format support into
the FILEIO backend.
It involves using a
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
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 it
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 device
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 fi
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
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 th
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
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. So
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 limitati
On 1/19/2014 4:44 AM, Nicholas A. Bellinger wrote:
From: Nicholas Bellinger
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 BLOCK APPLICATION TAG CHE
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,
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 to
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:
> > > >>O
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 tha
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, bu
This patch set is a lot of driver updates for qla4xxx, bfa, hpsa,
qla2xxx. It also removes the aic7xxx_old driver (which has been
deprecated for nearly a decade) and adds support for deadlines in error
handling.
The patch is available here:
git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi
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 ...
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 don'
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 b
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 > size here> on the same box. We could just go with the biggest size and
> > use the existing bh code for the sub-pagesized b
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 +
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
> > st
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 is
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 you.
Here is the usbmon log. The disk works with TV and Windows. No error messages.
Could it be under-powered?
Thanks,
Milan
88020e734600 2269960175 S Ci:3:001:0 s a3 00 0001 0004 4 <
88020e734600 2269960196 C Ci:3:001:0 0 4 = 0001
88020e734600 2269960200 S Ci:3:001:0 s a3 00
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 th
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 http://vger.kernel.or
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.
On Wed, 22 Jan 2014 11:30:19 -0800 James Bottomley
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 the pipe in the
> future that may
On Wed, 22 Jan 2014, Milan Svoboda wrote:
> Here is the usbmon log. The disk works with TV and Windows. No error messages.
> Could it be under-powered?
That's possible, but not if it works under Windows on the same
computer.
The first reset occurred when the disk failed to respond correctly to
On Wed, 2014-01-22 at 11:50 -0800, Andrew Morton wrote:
> On Wed, 22 Jan 2014 11:30:19 -0800 James Bottomley
> 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 surger
2014/1/7 James Bottomley
>
> On Mon, 2014-01-06 at 23:53 +0100, Matthias Eble wrote:
> > 2014/1/6 Lee Duncan :
> > > On 12/25/2013 03:00 PM, Matthias Eble wrote:
> > >> Here's the dmmp map
> > >> 360002aca6e6b dm-6 3PARdata,VV
> > >> size=2.0T features='0' hwhandler='0' wp=rw
>
> "Ric" == Ric Wheeler 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 4KB secto
> "James" == James Bottomley 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 for enterprise drives. The v
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,
>
>> 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 =
https://bugzilla.kernel.org/show_bug.cgi?id=60758
--- Comment #54 from Akemi Yagi ---
(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
> module compili
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,
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
> >>>
> >>> This patch adds support for D
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
> >
> > This patch adds support for DIF related CHECK_CONDITION ASC/ASCQ
> > exception cases into transport_send_check_condition_and_sense().
> >
> > This inclu
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 b
On 1/22/14 1:54 AM, "Bart Van Assche" wrote:
>On 01/16/14 23:35, Giridhar Malavali wrote:
>> On 1/10/14 10:27 AM, "Mike Snitzer" 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 interested to
>>> learn/di
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
th
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
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
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 ru
56 matches
Mail list logo
