svcadm(8)을 검색하려면 섹션에서 8 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.
ahci(4)
To compile this driver into the kernel, place the following lines
in your kernel configuration file: Alternatively, to load the
driver as a module at boot time, place the following line in
ahci_load="YES" The following tunables are settable from the con‐
trols Message Signaled Interrupts (MSI) usage by the specified
controller. MSI disabled; single MSI vector used, if supported;
multiple MSI vectors used, if supported (default); controls Com‐
mand Completion Coalescing (CCC) usage by the specified con‐
troller. Non-zero value enables CCC and defines maximum time (in
ms), request can wait for interrupt, if there are some more re‐
quests present on controller queue. CCC reduces number of con‐
text switches on systems with many parallel requests, but it can
decrease disk performance on some workloads due to additional
command latency. controls whether the driver should use direct
command completion from interrupt thread(s), or queue them to CAM
completion threads. Default value depends on number of MSI in‐
terrupts supported and number of implemented SATA ports. con‐
trols SATA interface Power Management for the specified channel,
allowing some power to be saved at the cost of additional command
latency. Possible values: interface Power Management is disabled
(default); device is allowed to initiate PM state change, host is
passive; host initiates PARTIAL PM state transition every time
port becomes idle; host initiates SLUMBER PM state transition
every time port becomes idle. driver initiates PARTIAL PM state
transition 1ms after port becomes idle; driver initiates SLUMBER
PM state transition 125ms after port becomes idle. Some con‐
trollers, such as ICH8, do not implement modes 2 and 3 with NCQ
used. Because of artificial entering latency, performance degra‐
dation in modes 4 and 5 is much smaller then in modes 2 and 3.
Note that interface Power Management complicates device presence
detection. A manual bus reset/rescan may be needed after device
hot-plug, unless hardware implements Cold Presence Detection.
setting to nonzero value limits maximum SATA revision (speed).
Values 1, 2 and 3 are respectively 1.5, 3 and 6Gbps. setting to
nonzero value forces driver attach to some known AHCI-capable
chips even if they are configured for legacy IDE emulation. De‐
fault is 1. This driver provides the subsystem with native ac‐
cess to the ports of AHCI-compatible controllers. Each SATA port
found is represented to CAM as a separate bus with one target,
or, if HBA supports Port Multipliers, 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 ATAPI devices are handled by the SCSI protocol
peripheral drivers etc. Driver features include support for Ser‐
ial ATA and ATAPI devices, Port Multipliers (including FIS-based
switching, when supported), hardware command queues (up to 32
commands per port), Native Command Queuing, SATA interface Power
Management, device hot-plug and Message Signaled Interrupts.
Driver supports "LED" enclosure management messages, defined by
the AHCI. When supported by hardware, it allows to control per-
port activity, locate and fault LEDs via the API or emulated de‐
vice for localization and status reporting purposes. Supporting
AHCI controllers may transmit that information to the backplane
controllers via SGPIO interface. Backplane controllers interpret
received statuses in some way (IBPI standard) to report them us‐
ing present indicators. The driver supports AHCI compatible con‐
trollers having PCI class 1 (mass storage), subclass 6 (SATA) and
programming interface 1 (AHCI). Also, in cooperation with ata‐
marvell and atajmicron drivers of ata(4), it supports AHCI part
of legacy-PATA + AHCI-SATA combined controllers, such as JMicron
JMB36x and Marvell 88SE61xx. activity LED device nodes fault LED
device nodes locate LED device nodes The driver first appeared in