sysfs-class-bdi 2.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566
  1. What: /sys/class/bdi/<bdi>/
  2. Date: January 2008
  3. Contact: Peter Zijlstra <[email protected]>
  4. Description:
  5. Provide a place in sysfs for the backing_dev_info object. This allows
  6. setting and retrieving various BDI specific variables.
  7. The <bdi> identifier can be either of the following:
  8. MAJOR:MINOR
  9. Device number for block devices, or value of st_dev on
  10. non-block filesystems which provide their own BDI, such as NFS
  11. and FUSE.
  12. MAJOR:MINOR-fuseblk
  13. Value of st_dev on fuseblk filesystems.
  14. default
  15. The default backing dev, used for non-block device backed
  16. filesystems which do not provide their own BDI.
  17. What: /sys/class/bdi/<bdi>/read_ahead_kb
  18. Date: January 2008
  19. Contact: Peter Zijlstra <[email protected]>
  20. Description:
  21. Size of the read-ahead window in kilobytes
  22. (read-write)
  23. What: /sys/class/bdi/<bdi>/min_ratio
  24. Date: January 2008
  25. Contact: Peter Zijlstra <[email protected]>
  26. Description:
  27. Under normal circumstances each device is given a part of the
  28. total write-back cache that relates to its current average
  29. writeout speed in relation to the other devices.
  30. The 'min_ratio' parameter allows assigning a minimum
  31. percentage of the write-back cache to a particular device.
  32. For example, this is useful for providing a minimum QoS.
  33. (read-write)
  34. What: /sys/class/bdi/<bdi>/max_ratio
  35. Date: January 2008
  36. Contact: Peter Zijlstra <[email protected]>
  37. Description:
  38. Allows limiting a particular device to use not more than the
  39. given percentage of the write-back cache. This is useful in
  40. situations where we want to avoid one device taking all or
  41. most of the write-back cache. For example in case of an NFS
  42. mount that is prone to get stuck, or a FUSE mount which cannot
  43. be trusted to play fair.
  44. (read-write)
  45. What: /sys/class/bdi/<bdi>/stable_pages_required
  46. Date: January 2008
  47. Contact: Peter Zijlstra <[email protected]>
  48. Description:
  49. If set, the backing device requires that all pages comprising a write
  50. request must not be changed until writeout is complete.
  51. (read-only)