The Linux Kernel

6.5.0

Quick search

Contents

  • A guide to the Kernel Development Process
  • Submitting patches: the essential guide to getting your code into the kernel
  • Code of conduct
  • Kernel Maintainer Handbook
  • All development-process docs
  • Core API Documentation
  • Driver implementer's API guide
  • Kernel subsystem documentation
    • Human interfaces
    • Storage interfaces
      • Filesystems in the Linux kernel
      • Block
      • CD-ROM
      • SCSI Subsystem
      • TCM Virtual Device
      • Driver implementer's API guide
      • Core API Documentation
      • Locking
      • Accounting
      • CPUFreq - CPU frequency and voltage scaling code in the Linux(TM) kernel
      • FPGA
      • I2C/SMBus Subsystem
      • Industrial I/O
      • ISDN
      • InfiniBand
      • LEDs
      • NetLabel
      • Networking
      • PCMCIA
      • Power Management
      • Timers
      • Serial Peripheral Interface (SPI)
      • 1-Wire Subsystem
      • Watchdog Support
      • Virtualization Support
      • Hardware Monitoring
      • Compute Accelerators
      • Security Documentation
      • Crypto API
      • Memory Management Documentation
      • BPF Documentation
      • USB support
      • PCI Bus Subsystem
      • Assorted Miscellaneous Devices Documentation
      • Scheduler
      • MHI
      • PECI Subsystem
      • WMI Subsystem
  • Locking in the kernel
  • Linux kernel licensing rules
  • How to write kernel documentation
  • Development tools for the kernel
  • Kernel Testing Guide
  • Kernel Hacking Guides
  • Linux Tracing Technologies
  • fault-injection
  • Kernel Livepatching
  • Rust
  • The Linux kernel user's and administrator's guide
  • The kernel build system
  • Reporting issues
  • User-space tools
  • The Linux kernel user-space API guide
  • The Linux kernel firmware guide
  • Open Firmware and Devicetree
  • CPU Architectures
  • Unsorted Documentation
  • Translations

This Page

  • Show Source

Link Power Managent PolicyΒΆ

This parameter allows the user to set the link (interface) power management. There are 3 possible options:

Value

Effect

min_power

Tell the controller to try to make the link use the least possible power when possible. This may sacrifice some performance due to increased latency when coming out of lower power states.

max_performance

Generally, this means no power management. Tell the controller to have performance be a priority over power management.

medium_power

Tell the controller to enter a lower power state when possible, but do not enter the lowest power state, thus improving latency over min_power setting.

©The kernel development community. | Powered by Sphinx 5.0.1 & Alabaster 0.7.12 | Page source