On 01/16/2014 09:48 PM, Alan Stern wrote:
> It's now clear that this is _not_ an XHCI issue, contrary to what
> $SUBJECT says.
>
> On Thu, 16 Jan 2014, Peter Palúch wrote:
>
>> Alan,
>>
>> I am attaching the usbmon trace after the drive has been plugged into
>> the USB-2 port. Record of the dri
On Fri, 2014-01-03 at 15:09 -0500, Martin K. Petersen wrote:
> > "nab" == Nicholas A Bellinger writes:
>
> nab> Given that bio_integrity_verify() is using bio_for_each_segment(),
> nab> the loop starts from the updated bio->bi_idx, and not a zero value,
> nab> which ends up skipping individua
On 1/16/14 7:12 AM, "Sagi Grimberg" wrote:
>Hey SCSI (and LSF) folks,
>
>I'd like to propose the following topic for upcoming LSF-MM:
>
>T10-PI standard is becoming more and more appealing for storage and
>cloud solutions.
>Since error-detection coding comes with its cost of CPU computation
>ov
Hello Linus,
Here are the outstanding target fixes for v3.13 code.
Please go ahead and pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git master
This series addresses a specific >= v3.12 regression related to the
iscsi-target percpu_ida conversion that has been r
You're right, staggered spinup is not enforced today when the disks
are behind several ATA ports. Only the disks behind a port multiplier
are spun up one at a time.
We are currently waiting for all the device(s) on the slowest port to
resume to continue.
Gwendal.
On Tue, Jan 14, 2014 at 1:45 PM, T
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/discuss areas that should become a development focus in the months
>following LSF.
+1 for scsi-mq.
--
On Thu, Jan 16, 2014 at 03:05:40PM -0500, Alan Stern wrote:
> On Thu, 16 Jan 2014, Todd E Brandt wrote:
>
> > > Does this plan sound reasonable to everyone? Are there important
> > > aspects I haven't considered (such as interactions between the SCSI and
> > > ATA layers)?
> > >
> > > Alan Stern
On Thu, 2014-01-16 at 20:54 +, Quinn Tran wrote:
> Nicholas,
>
> Comments inline. Thanks.
>
>
>
> >Bullet 3) Generating NPIV WWPN id: Qlogic overall strategy for this
> >question is: Qla2xxx driver is a common driver being used by various
> >hardware vendors(HP, IBM, Dell, etc..). Each ve
On Thu, 2014-01-16 at 17:12 +0200, Sagi Grimberg wrote:
> Hey SCSI (and LSF) folks,
>
> I'd like to propose the following topic for upcoming LSF-MM:
>
> T10-PI standard is becoming more and more appealing for storage and
> cloud solutions.
> Since error-detection coding comes with its cost of CP
Nicholas,
Comments inline. Thanks.
>Bullet 3) Generating NPIV WWPN id: Qlogic overall strategy for this
>question is: Qla2xxx driver is a common driver being used by various
>hardware vendors(HP, IBM, Dell, etc..). Each vendors have a different
>scheme on how to generate the WWPN value. QLog
It's now clear that this is _not_ an XHCI issue, contrary to what
$SUBJECT says.
On Thu, 16 Jan 2014, Peter Palúch wrote:
> Alan,
>
> I am attaching the usbmon trace after the drive has been plugged into
> the USB-2 port. Record of the drive in stall should occur around the
> file offset 8780
On Tue, Jan 14, 2014 at 01:27:25PM -0800, walt wrote:
> On 01/14/2014 09:20 AM, Sarah Sharp wrote:
> > On Mon, Jan 13, 2014 at 03:39:07PM -0800, walt wrote:
>
> >> Sarah, I just fixed my xhci bug for US$19.99 :)
> >>
> >> #lspci | tail -1
> >> 04:00.0 USB controller: NEC Corporation uPD720200 USB
On Thu, 16 Jan 2014, Phillip Susi wrote:
> On 1/16/2014 11:59 AM, Alan Stern wrote:
> > Since the START-STOP and TEST UNIT READY (or REQUEST SENSE or
> > whatever) commands are likely to take a long time, they should all
> > be carried out asynchronously with respect to the resume procedure.
> > I
On Thu, 16 Jan 2014, Todd E Brandt wrote:
> > Does this plan sound reasonable to everyone? Are there important
> > aspects I haven't considered (such as interactions between the SCSI and
> > ATA layers)?
> >
> > Alan Stern
> >
>
> Both approaches employ non-blocking resume of the scsi disks so
From: Mike Miller
This patch has every ID we have in our svn repository. Some controllers were
cancelled, others added, now the cancelled ones are back. Apparently the
debate rages on about which controllers are cancelled, which are not,
whatever. Please accept this patch. It is dependent upon th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/16/2014 11:59 AM, Alan Stern wrote:
> Since the START-STOP and TEST UNIT READY (or REQUEST SENSE or
> whatever) commands are likely to take a long time, they should all
> be carried out asynchronously with respect to the resume procedure.
> I don'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/16/2014 1:04 PM, Todd E Brandt wrote:
> Both approaches employ non-blocking resume of the scsi disks so why
> don't we treat these two patch sets as parts one and two. My patch
> just spins everything up but sets everything to non-blocking, so it
On Thu, Jan 16, 2014 at 11:59:43AM -0500, Alan Stern wrote:
> Folks:
>
> I would like to tie together separate email threads regarding disk
> spin-up time during system resume.
>
> Todd has posted some patches to make spin-up occur asynchronously, thus
> not delaying the return of the system to n
Folks:
I would like to tie together separate email threads regarding disk
spin-up time during system resume.
Todd has posted some patches to make spin-up occur asynchronously, thus
not delaying the return of the system to normal operation. Phillip and
I have been designing an approach to allow d
On 1/10/2014 8:27 PM, 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/discuss areas that should become a development focus in the months
following LSF.
+1 for scsi-mq.
--
To unsu
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 upstream for v3.13, exploring the remaining TODO
items towards an initial scsi-mq merge sometime before 2015 is upon us.
The benefits of scsi-mq re
This patch adds the DTS entries for the APM X-Gene SoC 15Gbps Multi-purpose
PHY driver. The PHY for SATA controller 2 and 3 are enabled by default.
Signed-off-by: Loc Ho
Signed-off-by: Tuan Phan
Signed-off-by: Suman Tripathi
---
arch/arm64/boot/dts/apm-storm.dtsi | 75 +++
This patch adds support for the APM X-Gene SoC SATA host controller. In
order for the host controller to work, the corresponding PHY driver
musts also be available.
v10:
* Update binding documentation
v9:
* Remove ACPI/EFI include files
* Remove the IO flush support, interrupt routine, and DTS
Signed-off-by: Loc Ho
Signed-off-by: Tuan Phan
Signed-off-by: Suman Tripathi
---
arch/arm64/boot/dts/apm-storm.dtsi | 75
1 files changed, 75 insertions(+), 0 deletions(-)
diff --git a/arch/arm64/boot/dts/apm-storm.dtsi
b/arch/arm64/boot/dts/apm-storm.dt
This patch exports functions required by APM X-Gene SoC SATA host
controller driver to avoid duplication of code.
Signed-off-by: Loc Ho
Signed-off-by: Tuan Phan
Signed-off-by: Suman Tripathi
---
drivers/ata/ahci.h|9 +
drivers/ata/libahci.c | 16 ++--
2 files chan
Signed-off-by: Loc Ho
Signed-off-by: Tuan Phan
Signed-off-by: Suman Tripathi
---
.../devicetree/bindings/phy/apm-xgene-phy.txt | 79
1 files changed, 79 insertions(+), 0 deletions(-)
create mode 100644 Documentation/devicetree/bindings/phy/apm-xgene-phy.txt
diff --
This patch adds function set_speed to the generic PHY framework operation
structure. This function can be called to instruct the PHY underlying layer
at specified lane to configure for specified speed in hertz.
Signed-off-by: Loc Ho
---
drivers/phy/phy-core.c | 21 +
inclu
This patch adds support for the APM X-Gene SoC SATA host controller driver.
It requires the corresponding APM X-Gene SoC PHY driver.
Signed-off-by: Loc Ho
Signed-off-by: Tuan Phan
Signed-off-by: Suman Tripathi
---
drivers/ata/Kconfig |8 +
drivers/ata/Makefile |1 +
drivers/at
Signed-off-by: Loc Ho
Signed-off-by: Tuan Phan
Signed-off-by: Suman Tripathi
---
.../devicetree/bindings/ata/apm-xgene.txt | 70
1 files changed, 70 insertions(+), 0 deletions(-)
create mode 100644 Documentation/devicetree/bindings/ata/apm-xgene.txt
diff --git
This patch adds support for APM X-Gene SoC 15Gbps Multi-purpose PHY. This
is the physical layer interface for the corresponding host controller. This
driver uses the new PHY generic framework posted by Kishon Vijay Abrahm.
In addition, the new PHY generic framework is patched to provide an
function
On 01/16/2014 11:15 AM, Viswas G wrote:
> From dfaae38ba7b6b7260fb3209d2dd12d70f0a8e306 Mon Sep 17 00:00:00 2001
> From: Suresh Thiagarajan
> Date: Thu, 16 Jan 2014 15:26:21 +0530
> Subject: [PATCH V2] pm80xx: Spinlock fix
>
> spin_lock_irqsave for the HBA lock is called in one function where fla
Hey SCSI (and LSF) folks,
I'd like to propose the following topic for upcoming LSF-MM:
T10-PI standard is becoming more and more appealing for storage and
cloud solutions.
Since error-detection coding comes with its cost of CPU computation
overhead,
state-of-the-art ASICs offer the ability to
On Thu, Jan 16, 2014 at 09:42:52AM +0100, Hannes Reinecke wrote:
> On 01/15/2014 11:39 PM, Stephen M. Cameron wrote:
> > From: Stephen M. Cameron
> >
> > On encountering unexpected error conditions from driver initiated
> > commands, print something useful like CDB and sense data rather than
> >
On Thu, 2014-01-16 at 14:26 +0200, sagi grimberg wrote:
>From:
> sagi grimberg
> To:
> linux-scsi
> ,
> target-devel
>
> Cc:
> Oren Duer
Actually, could you copy lsf...@lists.linux-foundation.org like the CFP
requests? The reason is quite simple
This commit generalizes isert_fast_reg_mr to receive mr
and frpl instead of fr_desc to do registration. In T10-PI
we also register protection memory region so we want to
use this routine.
This commit does not change any functionality.
Signed-off-by: Sagi Grimberg
---
drivers/infiniband/ulp/iser
In case the Target core passed transport T10 protection
operation:
1. Register data buffer (data memory region)
2. Register protection buffer if exsists (prot memory region)
3. Register signature region (signature memory region)
- use work request IB_WR_REG_SIG_MR
4. Execute RDMA
5. Upon RDMA c
This patchset adds basic support for T10-DIF protection information offload
in iSER target on top of Nic's recent work and RDMA signature verbs API.
This code was tested with my own implementation of the target core T10-PI
support
which was designed mainly to activate the transport DIF offload. I
Signed-off-by: Sagi Grimberg
---
include/target/target_core_base.h | 11 +--
1 files changed, 5 insertions(+), 6 deletions(-)
diff --git a/include/target/target_core_base.h
b/include/target/target_core_base.h
index d1b2435..5165cf7 100644
--- a/include/target/target_core_base.h
+++ b/
In case an iscsi portal group will be defined as t10_pi enabled,
all connections on top of it will support protected transactions.
T10-PI support may require extra reource allocation and maintenance by
the transport layer, so we don't want to apply them on non-t10_pi network
portals. This is a hoo
Upon connection establishment check if network portal is T10-PI
enabled and allocate T10-PI resources if necessary, allocate
signature enabled memory regions and mark connection queue-pair
as signature enabled.
Signed-off-by: Sagi Grimberg
---
drivers/infiniband/ulp/isert/ib_isert.c | 104 +
User may enable T10-PI support per network portal group. any connection
established on top of it, will be required to serve protected transactions.
Signed-off-by: Sagi Grimberg
---
drivers/target/iscsi/iscsi_target_configfs.c |6 ++
drivers/target/iscsi/iscsi_target_tpg.c | 19 +++
In case of protected transactions, we will need to check the
protection status of the transaction before sending SCSI response.
So be ready for RDMA_WRITE completions. currently we don't ask
for these completions, but for T10-PI we will.
Signed-off-by: Sagi Grimberg
---
drivers/infiniband/ulp/is
Hi Hannes,
Just want to chime in to clarify that in the case of a 'device reset', I think
the driver's use of LUN Reset to the Smart Array controller is the correct
choice here. This is because the 'device' is actually a single logical unit on
the controller (logical RAID volume). Sending a T
The loop 'for' in macro 'for_each_isci_host' (drivers/scsi/isci/init.c:717)
is executed more times than it can be. Regardless the condition:
'id < ARRAY_SIZE(to_pci_info(pdev)->hosts)' (drivers/scsi/isci/host.h:315)
it is executed when id equals ARRAY_SIZE(to_pci_info(pdev)->hosts) too.
(Remark:
Hey SCSI folks,
I'd like to propose the following topic for upcoming LSF-MM:
T10-PI standard is becoming more and more appealing for storage and
cloud solutions. Since error-detection
coding comes with its cost of CPU computation overhead, state-of-the-art
ASICs offer the ability to offload
T1
>From dfaae38ba7b6b7260fb3209d2dd12d70f0a8e306 Mon Sep 17 00:00:00 2001
From: Suresh Thiagarajan
Date: Thu, 16 Jan 2014 15:26:21 +0530
Subject: [PATCH V2] pm80xx: Spinlock fix
spin_lock_irqsave for the HBA lock is called in one function where flag
is local to that function. Another function is ca
On Wednesday 15 January 2014 15:59:27 Loc Ho wrote:
>
> May be I misread what Mark mentioned. The binding documentation should
> not specify the requirement of 0. And the binding of the dts should be
> as is:
>
> phy1 {
>#phy-cells = <1>;
> };
>
> sata1 {
>:::
>phys = <&phy1 0>;
megasas_get_map_info() might fail, after which it'll be
pointless to call megasas_sync_map_info().
So update megasas_get_map_info() to correctly handle errors
and call megasas_sync_map_info() only if no error occurred.
Cc: Kashyap Desai
Cc: Adam Radford
Signed-off-by: Hannes Reinecke
---
drive
Hi all,
recently I've enabled VT-d on one of my systems, which happened to have
one of the latest Megaraid SAS cards (Fury) installed.
And it failed miserably due to invalid DMAR tables.
Which would be okay, if just the HBA failed to initialize.
But the entire system stalled as the megaraid_sas dr
When megasas_get_pd_list() fails we cannot detect any drives,
so we should be checking the return value accordingly.
Cc: Kashyap Desai
Cc: Adam Radford
Signed-off-by: Hannes Reinecke
---
drivers/scsi/megaraid/megaraid_sas_base.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
di
When no HBA is found we should be returning '-ENXIO' to be consistent
with the other return values.
Cc: Kashyap Desai
Cc: Adam Radford
Signed-off-by: Hannes Reinecke
---
drivers/scsi/megaraid/megaraid_sas_fusion.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi
If the firmware is incommunicado for whatever reason the driver
will wait forever during initialisation, causing all sorts
of hangcheck timers to trigger.
We should rather wait for a defined time, and give up on the
command if no response was received.
Cc: Kashyap Desai
Cc: Adam Radford
Signed-o
The pointer to the queue info structure is potentially
a 64-bit value, so we should be using the correct macros
to set the values in the init frame.
Cc: Kashyap Desai
Cc: Adam Radford
Signed-off-by: Hannes Reinecke
---
drivers/scsi/megaraid/megaraid_sas_fusion.c | 5 -
1 file changed, 4 in
The syntax for the 'fire_cmd' callback is not used correctly,
so fix it up to be consistent with the original definition.
Cc: Kashyap Desai
Cc: Adam Radford
Signed-off-by: Hannes Reinecke
---
drivers/scsi/megaraid/megaraid_sas_fusion.c | 26 --
drivers/scsi/megaraid/meg
On 01/15/2014 11:39 PM, Stephen M. Cameron wrote:
> From: Stephen M. Cameron
>
> On encountering unexpected error conditions from driver initiated
> commands, print something useful like CDB and sense data rather than
> something useless like the kernel virtual address of the command buffer.
>
>
On 01/15/2014 11:38 PM, Stephen M. Cameron wrote:
> From: Scott Teel
>
> Signed-off-by: Scott Teel
> Acked-by: Stephen M. Cameron
> ---
> drivers/scsi/hpsa.c |9 +
> 1 files changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/scsi/hpsa.c b/drivers/scsi/hpsa.c
> index
56 matches
Mail list logo
