Skip to content

Commit

Permalink
---
Browse files Browse the repository at this point in the history
yaml
---
r: 95343
b: refs/heads/master
c: d67c6f8
h: refs/heads/master
i:
  95341: 474ac86
  95339: 9bb3274
  95335: 93dd05c
  95327: 1e4dff0
v: v3
  • Loading branch information
Linus Torvalds committed Apr 30, 2008
1 parent 893fb83 commit 670f82f
Show file tree
Hide file tree
Showing 388 changed files with 18,843 additions and 7,799 deletions.
2 changes: 1 addition & 1 deletion [refs]
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
---
refs/heads/master: 1175cdc670f2d4197b033f823b32435031a6daa8
refs/heads/master: d67c6f869c0a7f275689855161c93d714197e052
46 changes: 46 additions & 0 deletions trunk/Documentation/ABI/testing/sysfs-class-bdi
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
What: /sys/class/bdi/<bdi>/
Date: January 2008
Contact: Peter Zijlstra <a.p.zijlstra@chello.nl>
Description:

Provide a place in sysfs for the backing_dev_info object. This allows
setting and retrieving various BDI specific variables.

The <bdi> identifier can be either of the following:

MAJOR:MINOR

Device number for block devices, or value of st_dev on
non-block filesystems which provide their own BDI, such as NFS
and FUSE.

default

The default backing dev, used for non-block device backed
filesystems which do not provide their own BDI.

Files under /sys/class/bdi/<bdi>/
---------------------------------

read_ahead_kb (read-write)

Size of the read-ahead window in kilobytes

min_ratio (read-write)

Under normal circumstances each device is given a part of the
total write-back cache that relates to its current average
writeout speed in relation to the other devices.

The 'min_ratio' parameter allows assigning a minimum
percentage of the write-back cache to a particular device.
For example, this is useful for providing a minimum QoS.

max_ratio (read-write)

Allows limiting a particular device to use not more than the
given percentage of the write-back cache. This is useful in
situations where we want to avoid one device taking all or
most of the write-back cache. For example in case of an NFS
mount that is prone to get stuck, or a FUSE mount which cannot
be trusted to play fair.
2 changes: 1 addition & 1 deletion trunk/Documentation/DocBook/Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ DOCBOOKS := wanbook.xml z8530book.xml mcabook.xml videobook.xml \
kernel-api.xml filesystems.xml lsm.xml usb.xml kgdb.xml \
gadget.xml libata.xml mtdnand.xml librs.xml rapidio.xml \
genericirq.xml s390-drivers.xml uio-howto.xml scsi.xml \
mac80211.xml
mac80211.xml debugobjects.xml

###
# The build process is as follows (targets):
Expand Down
Loading

0 comments on commit 670f82f

Please sign in to comment.