I expect this is just a starting point for further discussion.
The mrsas driver appears to me to be excessively verbose, so I've made an initial patch to move some of the lines that appear more to be debugging under MRSAS_INFO and MRSAS_TRACE.
This patch reduces the default logging level, and moves several
print statements under mrsas_dprint.
Before:
AVAGO MegaRAID SAS FreeBSD mrsas driver version: 07.709.04.00-fbsd mrsas0: <BROADCOM AERO-10E2 SAS Controller> port 0x2000-0x20ff mem 0x9e400000-0x9e4fffff,0x9e500000-0x9e5fffff,0x9ea00000-0x9eafffff at device 0.0 numa-domain 0 on pci1 mrsas0: FW now in Ready state mrsas0: Using MSI-X with 128 number of vectors mrsas0: FW supports <128> MSIX vector,Online CPU 256 Current MSIX <128> mrsas0: mrsas_init_adapter: sc->reply_q_depth 0x27e0,sc->request_alloc_sz 0x9f60, sc->reply_alloc_sz 0x13f00,sc->io_frames_alloc_sz 0x13ee00 mrsas0: max sge: 0x106, max chain frame size: 0x1000, max fw cmd: 0x13ec sc->chain_frames_alloc_sz: 0x13ec000 mrsas0: Issuing IOC INIT command to FW. mrsas0: IOC INIT response received from FW. mrsas0: FW supports atomic descriptor: Yes mrsas0: NVME page size : (4096) mrsas0: FW supports JBOD Map mrsas0: FW supports JBOD Map Ext mrsas0: Jbod map is supported mrsas0: VD created target ID: 0xef mrsas0: FW supports: UnevenSpanSupport=1 mrsas0: max_fw_cmds: 5100 max_scsi_cmds: 5084 mrsas0: MSI-x interrupts setup success mrsas0: mrsas_ocr_thread
After:
Broadcom MegaRAID SAS mrsas driver version: 07.709.04.00-fbsd mrsas0: <BROADCOM AERO-10E2 SAS Controller> port 0x2000-0x20ff mem 0x9e400000-0x9e4fffff,0x9e500000-0x9e5fffff,0x9ea00000-0x9eafffff at device 0.0 numa-domain 3 on pci1 mrsas0: Using MSI-X with 128 vectors mrsas0: NVME page size: 4096 mrsas0: FW supports JBOD Map mrsas0: FW supports JBOD Map Ext mrsas0: FW supports: UnevenSpanSupport=1 mrsas0: max_fw_cmds: 5100 max_scsi_cmds: 5084