[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B6A08C587958942AA3002690DD4F8C30106B1DEB9@cosmail02.lsi.com>
Date: Wed, 24 Nov 2010 08:22:21 -0700
From: "Yang, Bo" <Bo.Yang@....com>
To: James Bottomley <James.Bottomley@...senPartnership.com>
CC: "'linux-scsi@...r.kernel.org'" <linux-scsi@...r.kernel.org>,
"'akpm@...l.org'" <akpm@...l.org>,
"'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>,
Tomas Henzl <thenzl@...hat.com>,
"Daftardar, Jayant" <Jayant.Daftardar@....com>,
"Prabhakaran, Rajesh" <Rajesh.Prabhakaran@....com>
Subject: RE: [PATCH 8/9] scsi: megaraid_sas - Driver take some workloads
from FW
James,
Our megaraid sas driver only implemented the part of the XOR calculation and copy capability(moving data between 2 buffers) for the RAID5 cmds which FW asks driver to do. When fw received very heavy I/Os and there are high pending cmds in FW, fw will ask the help from driver to finish some cmds and reduce the fw heavy load. Driver will only do part of the RAID5 (not take the jobs) from FW. Driver is not duplicating Parity calculation done on dm/md.
Thanks,
Bo Yang
-----Original Message-----
From: James Bottomley [mailto:James.Bottomley@...senPartnership.com]
Sent: Friday, November 19, 2010 12:53 PM
To: Yang, Bo
Cc: 'linux-scsi@...r.kernel.org'; 'akpm@...l.org'; 'linux-kernel@...r.kernel.org'; Tomas Henzl
Subject: Re: [PATCH 8/9] scsi: megaraid_sas - Driver take some workloads from FW
On Fri, 2010-11-19 at 10:43 -0700, Yang, Bo wrote:
> Driver added the new feature to take some of the workloads from FW to increase
> performance of the iMR controller. FW assigns the read cmds back to driver
> which will increase the performance for megaraid sas iMR controller.
Just on a process note: you don't have to cc me at every known
address ... I do read linux-scsi ...
My first take on this patch is that you're basically passing data back
to the kernel for RAID-N parity calculations. This effectively makes
your RAID one of those pseudo HW ones. In which case, why not simply
abandon the HW raid piece and have it all done by DM/MD, which are well
optimised for all types of RAID? The reason for asking is that we're
trying to reduce the number of in-kernel raid implementations and this
is going in the wrong direction.
James
Powered by blists - more mailing lists