MVS(4)

πŸ’– MVS(4) πŸ’–

okay bestie, sit DOWN, because today we're talking about mvs β€” the Marvell Serial ATA Host Controller driver β€” and she is lowkey iconic. this is the Kernel Interfaces Manual page, and i'm gonna walk you through every single crumb of it. no skips. periodt. ✨


🌸 NAME 🌸

mvs β€” Marvell Serial ATA Host Controller driver

like. that's her. that's the whole name. short, sweet, runs your SATA ports. πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

so if you wanna bake this driver into the kernel, you drop these lines into your kernel configuration file:

device pci
device scbus
device mvs

OR β€” and this is the fun lil alternative β€” you can load it as a module at boot time by putting this line in loader.conf(5):

mvs_load="YES"

and then there's the tunables, which you can set from loader(8). here's the whole roster, bestie, no gatekeeping:

  • hint.mvs.X.msi β€” controls Message Signaled Interrupts (MSI) usage by the specified controller.
  • hint.mvs.X.ccc β€” controls Command Completion Coalescing (CCC) usage by the specified controller. a non-zero value enables CCC and defines the maximum time (in us) that a request can wait for an interrupt. CCC reduces the number of context switches on systems with many parallel requests, but heads up β€” it can decrease disk performance on some workloads due to additional command latency. 😭
  • hint.mvs.X.cccc β€” defines the number of completed commands for CCC that trigger an interrupt without waiting for the specified coalescing timeout.
  • hint.mvsch.X.pm_level β€” controls SATA interface Power Management for the specified channel, letting you save a lil power at the cost of additional command latency. possible values, and yes i'm listing all of them:
    • 0 β€” interface Power Management is disabled (default);
    • 1 β€” device is allowed to initiate PM state change, host is passive;
    • 4 β€” driver initiates PARTIAL PM state transition 1ms after port becomes idle;
    • 5 β€” driver initiates SLUMBER PM state transition 125ms after port becomes idle.
⚠️ important, bestie: interface Power Management is not compatible with device presence detection. a manual bus reset is needed on device hot-plug. don't forget it or you'll be confused and sad. πŸ™ˆ
  • hint.mvsch.X.sata_rev β€” setting this to a nonzero value limits maximum SATA revision (speed). the values 1, 2 and 3 are respectively 1.5, 3 and 6Gbps.

πŸ¦‹ DESCRIPTION πŸ¦‹

so what does she actually DO? this driver gives the CAM(4) subsystem native access to the SATA ports of several generations β€” Gen-I/II/IIe β€” of Marvell SATA controllers. 🌈

every SATA port it finds is represented to CAM as a separate bus with one target, or β€” if the HBA supports Port Multipliers (Gen-II/IIe) β€” 16 targets. most of the bus-management details are handled by the SATA-specific transport of CAM. connected ATA disks are handled by the ATA protocol disk peripheral driver ada(4). ATAPI devices are handled by the SCSI protocol peripheral drivers cd(4), da(4), sa(4), etc.

driver features include, and this is her resume, and it EATS:

  • support for Serial ATA and ATAPI devices
  • Port Multipliers (including FIS-based switching, when supported)
  • hardware command queues (up to 31 command per port)
  • Native Command Queuing
  • SATA interface Power Management
  • device hot-plug
  • Message Signaled Interrupts

main character energy, honestly. πŸ‘‘


πŸ‘‘ HARDWARE πŸ‘‘

the mvs driver supports the following controllers:

Gen-I (SATA 1.5Gbps):

  • 88SX5040
  • 88SX5041
  • 88SX5080
  • 88SX5081

Gen-II (SATA 3Gbps, NCQ, PMP):

  • 88SX6040
  • 88SX6041 (including Adaptec 1420SA)
  • 88SX6080
  • 88SX6081

Gen-IIe (SATA 3Gbps, NCQ, PMP with FBS):

  • 88SX6042
  • 88SX7042 (including Adaptec 1430SA)
  • 88F5182 SoC
  • 88F6281 SoC
  • MV78100 SoC
🫢 note, that this hardware supports command queueing and FIS-based switching only for ATA DMA commands. ATAPI and non-DMA ATA commands are executed one by one for each port. that's just how it is, no cap.

⭐ SEE ALSO ⭐

ada(4), ata(4), cam(4), cd(4), da(4), sa(4)

go read them, they're all friends of hers, iykyk πŸ’œ


🌟 HISTORY 🌟

the mvs driver first appeared in FreeBSD 8.1. a whole era. a whole vibe. πŸŽ€


πŸ’• AUTHORS πŸ’•

Alexander Motin <mav@FreeBSD.org> β€” thank you king, we love you for this one 🫢


and that's the whole page, bestie!! you're now officially fluent in mvs πŸ’… this was the Debian build of the manual, dated March 23, 2015 β€” yes, she's an older icon but she still slays. now go forth and configure your SATA ports, you've got this fr fr. βœ¨πŸ¦‹πŸŒΈ

πŸ“¦ where this page comes from