> -----Original Message----- > From: linux-scsi-ow...@vger.kernel.org [mailto:linux-scsi- > ow...@vger.kernel.org] On Behalf Of Don Brace > Sent: Friday, November 11, 2016 8:48 AM > To: James Bottomley; Scott Benesh; James Bottomley; Martin K. Petersen > Cc: Viswas G; Mahesh Rajashekhara; h...@infradead.org; Scott Teel; Kevin > Barnett; Justin Lindley; elli...@hpe.com; linux-scsi@vger.kernel.org > Subject: RE: [PATCH V4 2/2] aacraid: remove wildcard for series 9 controllers > > EXTERNAL EMAIL > > > > -----Original Message----- > > From: James Bottomley > [mailto:james.bottom...@hansenpartnership.com] > > Sent: Thursday, September 08, 2016 5:38 PM > > To: Scott Benesh; James Bottomley; Don Brace; Martin K. Petersen > > Cc: Viswas G; Mahesh Rajashekhara; h...@infradead.org; Scott Teel; Kevin > > Barnett; Justin Lindley; elli...@hpe.com; linux-scsi@vger.kernel.org > > Subject: RE: [PATCH V4 2/2] aacraid: remove wildcard for series 9 > controllers > > > > EXTERNAL EMAIL > > > > > > On September 8, 2016 2:33:52 PM EDT, Scott Benesh > > <scott.ben...@microsemi.com> wrote: > > >> > > >> On Thu, 2016-09-08 at 18:15 +0000, Don Brace wrote: > > >> > > > - { 0x9005, 0x028f, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 65 }, /* > > >> > > > Adaptec PMC > > >> > > > Series 9 */ > > >> > > > > > >> > > > How are people that load aacraid in their initrd going to boot > > >> > > > after this? > > >> > > > > > >> > > > -- > > >> > > > Martin K. Petersen Oracle Linux Engineering > > >> > > > > >> > > I updated smartpqi/Kconfig and added > > >Documentation/scsi/smartpqi.txt > > >> > > to inform users of the need to configure the smartpqi driver > > >moving > > >> > > forward for aacraid Series 9 controllers. > > >> > > > > >> > > Hope this helps. > > >> > > >> That's not going to be enough: this ID has been in the aacriad driver > > >since > > >> 2011. That means anyone who finally gets hold of one of these new > > >cards > > >> but uses a distro that doesn't have the new smartpqi driver will be > > >attached > > >> via the aacraid one. > > >> > > > > > >That's ok because for previous distros the new controller will work > > >with the previous aacraid driver, although with non-optimal > > >performance. > > > > Not after this change hits. Then systems that only have aacraid in the > > initrd > > will fail to boot. > > > > >What we want to do is sync up at 4.9 so going forward only the new > > >smartpqi driver will attach to these new controllers. > > > > So you have a plan in place with the distros to migrate the initrd images? > > Without being told, some will only install the modules the previous initrd > was > > configured for. > > > > James > > > > >Scott > > > > > >> Given that the life times of enterprise distributions is two years > > >and you're > > >> releasing this smartpqi soon, the overlap is unavoidable. > > >> > > >> James > > >> > > > > The ID we want to remove from the aacraid driver will not be available until > Q1 next year, > so no customer currently has it yet. If they are running an older kernel, the > aacraid driver > will support this ID but in 'sync' mode, their servers will continue to boot. > > If they upgrade to a newer kernel and do not know to configure the > smartpqi > driver and the system fails to boot, they can fall back to the previous > kernel and configure the smartpqi driver. > > This patch is for newer kernels going forward. We need to eliminate the > duplication for newer kernels. If both drivers support the same ID > they will have to know how to rebuild their initrd with a specific driver > order. Customers that have servers configured with both older aacraid > devices > and the newer smartpqi devices will definitely have to do this. Having to > rebuild the kernel with smartpqi enabled would seem to be an easier > customer experience. > > The officially supported driver for this ID is smartpqi. > > Thanks, > Don Brace > > ESC - Smart Storage > Microsemi Corporation > > > Can there be any movement on this patch?
Thanks, Don Brace ESC - Smart Storage Microsemi Corporation
