Добрый день.
Если вопрос аренды помещения еще актуален для Вас?
Хочу предложить помещения в аренду: площадью от 16 М2 по реально низкой
арендной ставке (без комиссии) в наших бизнес-центрах, рядом со станциями метро:
- Китай-город
- Лубянка
- Площадь революции
- Новые Черемушки
-
This is a set of 8 fixes. Two are trivial gcc-6 updates (brace
additions and unused variable removal). There's a couple of cxlflash
regressions, a correction for sd being overly chatty on revalidation
(causing excess log increases). A VPD issue which could crash USB
devices because they seem
>
> On 4/7/2016 10:15 PM, Winkler, Tomas wrote:
> > On Wed, 2016-04-06 at 09:51 +0100, Joao Pinto wrote:
> >> Hi!
> >>
> >> On 4/4/2016 12:11 PM, Tomas Winkler wrote:
> >>> Register UFS RPMB LUN with the RPMB subsystem and provide
> >>> implementation for the RPMB access operations. RPMB
On Fri, Apr 08 2016 at 7:42am -0400,
Johannes Thumshirn wrote:
> Ladies and Gentlemen,
> To show off some numbers from our testing:
>
> All tests are performed against the cache of the Array, not the disks as we
> wanted to test the Linux stack not the Disk Array.
>
> All
On Fri, 2016-04-08 at 13:40 -0400, Matthew Wilcox wrote:
> On Fri, Apr 08, 2016 at 01:29:26PM +0200, Hannes Reinecke wrote:
> > - Interrupt steering needs to be controlled by block-mq instead of
> the driver. It's pointless to have each driver implement its own
> policies on interrupt
Simple change, looks fine to me.
Reviewed-by: Laurence Oberman
Laurence Oberman
Principal Software Maintenance Engineer
Red Hat Global Support Services
- Original Message -
From: "Denys Vlasenko"
To: "James Bottomley"
This function compiles to 511 bytes of machine code.
Abort commands are not time-critical at all.
Signed-off-by: Denys Vlasenko
CC: James Bottomley
CC: Hiral Patel
CC: Suma Ramars
CC: Brian
On Mon, Apr 4, 2016 at 5:00 PM, Hannes Reinecke wrote:
> Hi all,
>
> here's a patchset implementing SMR (shingled magnetic recording)
> device support for the block and SCSI layer.
>
> There are two main parts to it:
> - mapping the 'RESET WRITE POINTER' command to the 'discard'
On Fri, 2016-04-08 at 20:08 +0200, Christoph Hellwig wrote:
> On Fri, Apr 08, 2016 at 11:00:51AM -0700, James Bottomley wrote:
> > > - Inability to use all queues supported by a device. Intel's
> > > P3700
> > >supports 31 queues, but block-mq insists on assigning an even
> > > multiple
> >
On 04/08/2016 03:30 PM, Sebastian Andrzej Siewior wrote:
> On 03/15/2016 09:19 AM, Christoph Hellwig wrote:
>> On Fri, Mar 11, 2016 at 05:32:15PM +0100, Sebastian Andrzej Siewior wrote:
>>> alloc_workqueue() in setup and then queue_work_on(cpu, , item)? item
>>> should be struct work_struct but
On 04/08/2016 10:40 AM, Matthew Wilcox wrote:
- Interrupt steering needs to be controlled by block-mq instead of
the driver. It's pointless to have each driver implement its own
policies on interrupt steering, irqbalanced remains a source of
end-user frustration, and block-mq can
First: what is actually FC specific here?
> - timeout handling:
> Out of necessity the status of any timed out command is undefined.
> So to be absolutely safe HBAs will be using extended timeouts here
> (eg 70secs for lpfc). During that time we _could_ signal I/O timeout
> to the upper layers,
On Fri, Apr 08, 2016 at 11:00:51AM -0700, James Bottomley wrote:
> > - Inability to use all queues supported by a device. Intel's P3700
> >supports 31 queues, but block-mq insists on assigning an even multiple
> >of CPUs to each queue. So if you have 48 CPUs, it will use 24 queues.
> >
On Fri, Apr 08, 2016 at 01:40:06PM -0400, Matthew Wilcox wrote:
> - Inability to use all queues supported by a device. Intel's P3700
>supports 31 queues, but block-mq insists on assigning an even multiple
>of CPUs to each queue. So if you have 48 CPUs, it will use 24 queues.
>If you
On Fri, 2016-04-08 at 13:40 -0400, Matthew Wilcox wrote:
> On Fri, Apr 08, 2016 at 01:29:26PM +0200, Hannes Reinecke wrote:
> > I'd like to propose a topic on block-mq issues with FC.
> > During my performance testing using block/scsi-mq with FC I've hit
> > several issues I'd like to discuss:
>
On Fri, Apr 08, 2016 at 01:29:26PM +0200, Hannes Reinecke wrote:
> I'd like to propose a topic on block-mq issues with FC.
> During my performance testing using block/scsi-mq with FC I've hit
> several issues I'd like to discuss:
If there's a general block-mq bitching session, I have some ideas
Hi,
On 4/7/2016 10:15 PM, Winkler, Tomas wrote:
> On Wed, 2016-04-06 at 09:51 +0100, Joao Pinto wrote:
>> Hi!
>>
>> On 4/4/2016 12:11 PM, Tomas Winkler wrote:
>>> Register UFS RPMB LUN with the RPMB subsystem and provide
>>> implementation for the RPMB access operations. RPMB partition is
>>>
On 04/08/2016 04:29 AM, Hannes Reinecke wrote:
I'd like to propose a topic on block-mq issues with FC.
During my performance testing using block/scsi-mq with FC I've hit
several issues I'd like to discuss:
- timeout handling:
Out of necessity the status of any timed out command is undefined.
So
On Fri, 2016-04-08 at 11:51 -0400, Ewan D. Milne wrote:
> On Fri, 2016-04-08 at 08:11 -0700, James Bottomley wrote:
> > On Fri, 2016-04-08 at 13:29 +0200, Hannes Reinecke wrote:
> > > Hi all,
> > >
> > > I'd like to propose a topic on block-mq issues with FC.
> > > During my performance testing
On Fri, 2016-04-08 at 08:11 -0700, James Bottomley wrote:
> On Fri, 2016-04-08 at 13:29 +0200, Hannes Reinecke wrote:
> > Hi all,
> >
> > I'd like to propose a topic on block-mq issues with FC.
> > During my performance testing using block/scsi-mq with FC I've hit
> > several issues I'd like to
We are dereferencing ioc->sense_dma_pool in pci_pool_free() and after
that we are checking if it is NULL, before calling pci_pool_destroy().
Lets check if it is NULL before calling both pci_pool_free() and
pci_pool_destroy().
Signed-off-by: Sudip Mukherjee
---
On Fri, 2016-04-08 at 13:29 +0200, Hannes Reinecke wrote:
> Hi all,
>
> I'd like to propose a topic on block-mq issues with FC.
> During my performance testing using block/scsi-mq with FC I've hit
> several issues I'd like to discuss:
>
> - timeout handling:
> Out of necessity the status of any
On 03/15/2016 09:19 AM, Christoph Hellwig wrote:
> On Fri, Mar 11, 2016 at 05:32:15PM +0100, Sebastian Andrzej Siewior wrote:
>> alloc_workqueue() in setup and then queue_work_on(cpu, , item)? item
>> should be struct work_struct but all I have is a skb. Is there an easy
>> way to get this
Hi Ewan,
OK, that makes sense.
I suspected after everybody's responses that RHEL was somehow ignoring the
array imposed limit here.
I actually got lucky because I needed to be able to issue 4MB IO'S to reproduce
the failures seen
at the customer on the initiator side.
Looking at the
The version of RHEL you are using does not have:
commit ca369d51b3e1649be4a72addd6d6a168cfb3f537
Author: Martin K. Petersen
Date: Fri Nov 13 16:46:48 2015 -0500
block/sd: Fix device-imposed transfer length limits
(which will be added during the next update).
Ladies and Gentlemen,
To show off some numbers from our testing:
All tests are performed against the cache of the Array, not the disks as we
wanted to test the Linux stack not the Disk Array.
All single queue tests have been performed with the deadline I/O Scheduler.
Comments welcome, have fun
Hi all,
I'd like to propose a topic on block-mq issues with FC.
During my performance testing using block/scsi-mq with FC I've hit
several issues I'd like to discuss:
- timeout handling:
Out of necessity the status of any timed out command is undefined.
So to be absolutely safe HBAs will be
On 4/7/2016 10:15 PM, Winkler, Tomas wrote:
> On Wed, 2016-04-06 at 09:51 +0100, Joao Pinto wrote:
>> Hi!
>>
>> On 4/4/2016 12:11 PM, Tomas Winkler wrote:
>>> Register UFS RPMB LUN with the RPMB subsystem and provide
>>> implementation for the RPMB access operations. RPMB partition is
>>> accessed
Hi,
On 4/7/2016 10:15 PM, Winkler, Tomas wrote:
> On Wed, 2016-04-06 at 09:51 +0100, Joao Pinto wrote:
>> Hi!
>>
>> On 4/4/2016 12:11 PM, Tomas Winkler wrote:
>>> Register UFS RPMB LUN with the RPMB subsystem and provide
>>> implementation for the RPMB access operations. RPMB partition is
>>>
Hi!
On 4/7/2016 10:15 PM, Winkler, Tomas wrote:
> On Wed, 2016-04-06 at 09:51 +0100, Joao Pinto wrote:
>> Hi!
>>
>> On 4/4/2016 12:11 PM, Tomas Winkler wrote:
>>> Register UFS RPMB LUN with the RPMB subsystem and provide
>>> implementation for the RPMB access operations. RPMB partition is
>>>
Hi Rob,
On 4/7/2016 6:57 PM, Rob Herring wrote:
> On Mon, Apr 04, 2016 at 11:48:23AM +0100, Joao Pinto wrote:
>>
>> Hi Rob,
>>
>> On 4/4/2016 6:15 AM, Rob Herring wrote:
>>> On Thu, Mar 31, 2016 at 07:57:21PM +0100, Joao Pinto wrote:
This patch adds a glue platform driver for the Synopsys
This patch fixes the ITCT table setup as it should be
configured differently for SAS and SATA devices.
For SATA disks there is no need to set qw2 (already
zeroed).
Also, link parameters for Bus inactive limit, max
connection time limit, and reject to open limit timers
parameters are changed to
This patch adds support for directly attaching SATA
disks to phy 4-8. The problem was that only registers
concerned with phy 0-3 were being considered in
sata_int_v2_hw().
The issue was not detected previously as the
development board only exposed phy 0-3; the new
board provides access to 8 phys.
Intermittently it is found that when multiple SATA
disks are directly connected to the host that some
disks are not detected.
The problem is that all set bitfields in ENT_INT_SRC1
are cleared for all phys in sata_int_v2_hw() - it
should clear the set bit for the phy being serviced.
Also
Signed-off-by: John Garry
---
drivers/scsi/hisi_sas/hisi_sas.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/hisi_sas/hisi_sas.h b/drivers/scsi/hisi_sas/hisi_sas.h
index 29e89f3..7a7e543 100644
--- a/drivers/scsi/hisi_sas/hisi_sas.h
+++
This patchset introduces SATA support fixes for
the HiSilicon v2 hw SAS controller.
Fixes include:
- attach issue for SATA disk attached through expander
- intermittent issue for directly attaching multiple
SATA disks
- add support for directly attaching SATA disk to phy
index 4+
- ITCT config
Contrary to the field name, the MCR (max connection rate)
in the ITCT should hold the device linkrate (linkrate of
the connected phy), and not the max linkrate.
This fixes an issue seen where some SATA drives connected
through an expander which would not attach.
Signed-off-by: John Garry
Hello Nicholas
Using fedora here and LIO/
The same array is used in testing the RHEL and upstream kernels.
Linux fedstorage 4.5.0-rc7+ #1 SMP Sun Mar 13 16:30:39 EDT 2016 x86_64 x86_64
x86_64 GNU/Linux
I have 3 NVME cards striped in an LVM configuration and I create the block
devices using
Hi Bart
"Have you already tried to set the max_sect parameter in
/etc/srp_daemon.conf (assuming you are using srptools >= 1.0.3 for SRP
login) ? Additionally, writing something like "options ib_srp
cmd_sg_entries=255" into /etc/modprobe.d/ib_srp.conf will increase the
maximum SRP transfer size.
"
On Sun, 2016-03-13 at 17:43 +0530, Varun Prakash wrote:
> On Fri, Mar 11, 2016 at 10:28:33PM -0800, Nicholas A. Bellinger wrote:
> > Hi Varun & Co,
> >
> > On Mon, 2016-03-07 at 15:22 -0800, Nicholas A. Bellinger wrote:
> >
> >
> >
> > > So obviously this is going to take longer to sort out,
zfcp has its own mechanism for selective scanning, so revert to
the original scanning behaviour to not confuse users.
Fixes: 4e91e876e9b8b6eb4255aa0d690778a89d3f1d28
Suggested-by: Benjamin Block
Signed-off-by: Hannes Reinecke
---
41 matches
Mail list logo