sysfs-class-scsi_host 4.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119
  1. What: /sys/class/scsi_host/hostX/isci_id
  2. Date: June 2011
  3. Contact: Dave Jiang <[email protected]>
  4. Description:
  5. This file contains the enumerated host ID for the Intel
  6. SCU controller. The Intel(R) C600 Series Chipset SATA/SAS
  7. Storage Control Unit embeds up to two 4-port controllers in
  8. a single PCI device. The controllers are enumerated in order
  9. which usually means the lowest number scsi_host corresponds
  10. with the first controller, but this association is not
  11. guaranteed. The 'isci_id' attribute unambiguously identifies
  12. the controller index: '0' for the first controller,
  13. '1' for the second.
  14. What: /sys/class/scsi_host/hostX/acciopath_status
  15. Date: November 2013
  16. Contact: Stephen M. Cameron <[email protected]>
  17. Description: This file contains the current status of the "SSD Smart Path"
  18. feature of HP Smart Array RAID controllers using the hpsa
  19. driver. SSD Smart Path, when enabled permits the driver to
  20. send i/o requests directly to physical devices that are part
  21. of a logical drive, bypassing the controllers firmware RAID
  22. stack for a performance advantage when possible. A value of
  23. '1' indicates the feature is enabled, and the controller may
  24. use the direct i/o path to physical devices. A value of zero
  25. means the feature is disabled and the controller may not use
  26. the direct i/o path to physical devices. This setting is
  27. controller wide, affecting all configured logical drives on the
  28. controller. This file is readable and writable.
  29. What: /sys/class/scsi_host/hostX/link_power_management_policy
  30. Date: Oct, 2007
  31. KernelVersion: v2.6.24
  32. Contact: [email protected]
  33. Description:
  34. (RW) This parameter allows the user to read and set the link
  35. (interface) power management.
  36. There are four possible options:
  37. min_power: Tell the controller to try to make the link use the
  38. least possible power when possible. This may sacrifice some
  39. performance due to increased latency when coming out of lower
  40. power states.
  41. max_performance: Generally, this means no power management.
  42. Tell the controller to have performance be a priority over power
  43. management.
  44. medium_power: Tell the controller to enter a lower power state
  45. when possible, but do not enter the lowest power state, thus
  46. improving latency over min_power setting.
  47. med_power_with_dipm: Identical to the existing medium_power
  48. setting except that it enables dipm (device initiated power
  49. management) on top, which makes it match the Windows IRST (Intel
  50. Rapid Storage Technology) driver settings. This setting is also
  51. close to min_power, except that:
  52. a) It does not use host-initiated slumber mode, but it does
  53. allow device-initiated slumber
  54. b) It does not enable low power device sleep mode (DevSlp).
  55. What: /sys/class/scsi_host/hostX/em_message
  56. What: /sys/class/scsi_host/hostX/em_message_type
  57. Date: Jun, 2008
  58. KernelVersion: v2.6.27
  59. Contact: [email protected]
  60. Description:
  61. em_message: (RW) Enclosure management support. For the LED
  62. protocol, writes and reads correspond to the LED message format
  63. as defined in the AHCI spec.
  64. The user must turn sw_activity (under `/sys/block/*/device/`)
  65. OFF it they wish to control the activity LED via the em_message
  66. file.
  67. em_message_type: (RO) Displays the current enclosure management
  68. protocol that is being used by the driver (for eg. LED, SAF-TE,
  69. SES-2, SGPIO etc).
  70. What: /sys/class/scsi_host/hostX/ahci_port_cmd
  71. What: /sys/class/scsi_host/hostX/ahci_host_caps
  72. What: /sys/class/scsi_host/hostX/ahci_host_cap2
  73. Date: Mar, 2010
  74. KernelVersion: v2.6.35
  75. Contact: [email protected]
  76. Description:
  77. [to be documented]
  78. What: /sys/class/scsi_host/hostX/ahci_host_version
  79. Date: Mar, 2010
  80. KernelVersion: v2.6.35
  81. Contact: [email protected]
  82. Description:
  83. (RO) Display the version of the AHCI spec implemented by the
  84. host.
  85. What: /sys/class/scsi_host/hostX/em_buffer
  86. Date: Apr, 2010
  87. KernelVersion: v2.6.35
  88. Contact: [email protected]
  89. Description:
  90. (RW) Allows access to AHCI EM (enclosure management) buffer
  91. directly if the host supports EM.
  92. For eg. the AHCI driver supports SGPIO EM messages but the
  93. SATA/AHCI specs do not define the SGPIO message format of the EM
  94. buffer. Different hardware(HW) vendors may have different
  95. definitions. With the em_buffer attribute, this issue can be
  96. solved by allowing HW vendors to provide userland drivers and
  97. tools for their SGPIO initiators.
  98. What: /sys/class/scsi_host/hostX/em_message_supported
  99. Date: Oct, 2009
  100. KernelVersion: v2.6.39
  101. Contact: [email protected]
  102. Description:
  103. (RO) Displays supported enclosure management message types.