Re: mfii0 kudos to bouyer@ Was Re: dmesg | grep -c "not configured" = 240...

[Mike Pumford <mpumford%mudcovered.org.uk@localhost>]

On 04/12/2018 20:22, Manuel Bouyer wrote:
> On Tue, Dec 04, 2018 at 07:17:59PM +0000, Mike Pumford wrote:
> > On 03/12/2018 22:47, Manuel Bouyer wrote:
> > > Hello,
> > > I synced our mpii(4) driver with the latest OpenBSD one and commited to HEAD.
> > > I tested it with a SAS2 controller (I don't have SAS3 ones), so it would be
> > > good if someone could test a SAS3 with some drives (the command setup is
> > > different between SAS2 and SAS3, this is the code path I can't test).
> > Tested with my SAS3 card and an enclosure. Relevent dmesg bits are:
> >
> > mpii0 at pci1 dev 0 function 0: vendor 1000 product 0097 (rev. 0x01)
> > mpii0: interrupting at msi0 vec 0
> > mpii0: SAS9300-8e, firmware 0.250.110.0, MPI 2.5
> >
> > scsibus0 at mpii0: 768 targets, 8 luns per target
> > scsibus0: waiting 2 seconds for devices to settle...
> > sd0 at scsibus0 target 0 lun 0: <SEAGATE, ST32000444SS, XQB7> disk fixed
> > sd1 at scsibus0 target 1 lun 0: <SEAGATE, ST32000444SS, XQB7> disk fixed
> > sd2 at scsibus0 target 2 lun 0: <SEAGATE, ST32000444SS, XQB7> disk fixed
> > sd3 at scsibus0 target 3 lun 0: <SEAGATE, ST32000444SS, XQB7> disk fixed
> > sd4 at scsibus0 target 4 lun 0: <SEAGATE, ST32000444SS, XQB7> disk fixed
> > sd5 at scsibus0 target 5 lun 0: <SEAGATE, ST32000444SS, XQB7> disk fixed
> > sd6 at scsibus0 target 6 lun 0: <SEAGATE, ST32000444SS, XQB7> disk fixed
> > sd7 at scsibus0 target 7 lun 0: <SEAGATE, ST32000444SS, XQB7> disk fixed
> > sd8 at scsibus0 target 8 lun 0: <SEAGATE, ST32000444SS, XQB7> disk fixed
> > sd9 at scsibus0 target 9 lun 0: <SEAGATE, ST32000444SS, XQB7> disk fixed
> > sd10 at scsibus0 target 10 lun 0: <SEAGATE, ST32000444SS, XQB7> disk fixed
> > sd11 at scsibus0 target 11 lun 0: <SEAGATE, ST32000444SS, XQB7> disk fixed
> > sd12 at scsibus0 target 12 lun 0: <SEAGATE, ST32000444SS, XQB7> disk fixed
> > sd13 at scsibus0 target 13 lun 0: <SEAGATE, ST32000444SS, XQB7> disk fixed
> > sd14 at scsibus0 target 14 lun 0: <SEAGATE, ST32000444SS, XQB7> disk fixed
> > sd15 at scsibus0 target 15 lun 0: <SEAGATE, ST32000444SS, XQB7> disk fixed
> > sd16 at scsibus0 target 16 lun 0: <SEAGATE, ST32000444SS, XQB7> disk fixed
> > sd17 at scsibus0 target 17 lun 0: <SEAGATE, ST32000444SS, XQB7> disk fixed
> >
> > Did some IO to the disks and got read/write performance at exactly the
> > speeds I'd expect >170MB/s read and a little less for writing.
>
> Was it with one disk, or several disks at once ?
> I get 80MB/s with a SATA SEAGATE ST375064 (750GB). With a newer controller
> and that much disk, I'd expect more than 170MB/s if several disks are used
> in parallel.
It was just the one disk and its a SAS2 drive behind some SAS2 expanders 
so we aren't taking full advantage of the SAS3 speed. Sadly all the SAS3 
drives I have access to are actually in use for real work. :(

I will try a multi-drive test when I'm in the office again on Thursday.

The 170MB is exactly the performance I'd expect for that drive and 
matches what it achieves in linux on the same hardware.

> Disk insertion are working with my controller, I've not tested removal yet
> (will do tomorow). More testing is always welcome :)
Okay I'll also do some power down/power up cycles on some of the drive 
bays in the enclosure which should test removal and insertion. The 
driver was definately reporting the SAS discovery events. I'll have a 
look at the PCI IDs in the other spare SAS3 systems to see if that will 
test any of the other new bits of code as well.

Mike