Loading Documentation/block/switching-sched.txt 0 → 100644 +22 −0 Original line number Original line Diff line number Diff line As of the Linux 2.6.10 kernel, it is now possible to change the IO scheduler for a given block device on the fly (thus making it possible, for instance, to set the CFQ scheduler for the system default, but set a specific device to use the anticipatory or noop schedulers - which can improve that device's throughput). To set a specific scheduler, simply do this: echo SCHEDNAME > /sys/block/DEV/queue/scheduler where SCHEDNAME is the name of a defined IO scheduler, and DEV is the device name (hda, hdb, sga, or whatever you happen to have). The list of defined schedulers can be found by simply doing a "cat /sys/block/DEV/queue/scheduler" - the list of valid names will be displayed, with the currently selected scheduler in brackets: # cat /sys/block/hda/queue/scheduler noop anticipatory deadline [cfq] # echo anticipatory > /sys/block/hda/queue/scheduler # cat /sys/block/hda/queue/scheduler noop [anticipatory] deadline cfq Documentation/cpu-freq/index.txt +1 −1 Original line number Original line Diff line number Diff line Loading @@ -53,4 +53,4 @@ the CPUFreq Mailing list: * http://lists.linux.org.uk/mailman/listinfo/cpufreq * http://lists.linux.org.uk/mailman/listinfo/cpufreq Clock and voltage scaling for the SA-1100: Clock and voltage scaling for the SA-1100: * http://www.lart.tudelft.nl/projects/scaling * http://www.lartmaker.nl/projects/scaling Documentation/feature-removal-schedule.txt +3 −2 Original line number Original line Diff line number Diff line Loading @@ -25,8 +25,9 @@ Who: Adrian Bunk <bunk@stusta.de> --------------------------- --------------------------- What: drivers depending on OBSOLETE_OSS_DRIVER What: drivers that were depending on OBSOLETE_OSS_DRIVER When: January 2006 (config options already removed) When: before 2.6.19 Why: OSS drivers with ALSA replacements Why: OSS drivers with ALSA replacements Who: Adrian Bunk <bunk@stusta.de> Who: Adrian Bunk <bunk@stusta.de> Loading Documentation/filesystems/sysfs.txt +5 −0 Original line number Original line Diff line number Diff line Loading @@ -246,6 +246,7 @@ class/ devices/ devices/ firmware/ firmware/ net/ net/ fs/ devices/ contains a filesystem representation of the device tree. It maps devices/ contains a filesystem representation of the device tree. It maps directly to the internal kernel device tree, which is a hierarchy of directly to the internal kernel device tree, which is a hierarchy of Loading @@ -264,6 +265,10 @@ drivers/ contains a directory for each device driver that is loaded for devices on that particular bus (this assumes that drivers do not for devices on that particular bus (this assumes that drivers do not span multiple bus types). span multiple bus types). fs/ contains a directory for some filesystems. Currently each filesystem wanting to export attributes must create its own hierarchy below fs/ (see ./fuse.txt for an example). More information can driver-model specific features can be found in More information can driver-model specific features can be found in Documentation/driver-model/. Documentation/driver-model/. Loading Documentation/vm/hugetlbpage.txt +10 −1 Original line number Original line Diff line number Diff line Loading @@ -32,7 +32,16 @@ The output of "cat /proc/meminfo" will have lines like: ..... ..... HugePages_Total: xxx HugePages_Total: xxx HugePages_Free: yyy HugePages_Free: yyy Hugepagesize: zzz KB HugePages_Rsvd: www Hugepagesize: zzz kB where: HugePages_Total is the size of the pool of hugepages. HugePages_Free is the number of hugepages in the pool that are not yet allocated. HugePages_Rsvd is short for "reserved," and is the number of hugepages for which a commitment to allocate from the pool has been made, but no allocation has yet been made. It's vaguely analogous to overcommit. /proc/filesystems should also show a filesystem of type "hugetlbfs" configured /proc/filesystems should also show a filesystem of type "hugetlbfs" configured in the kernel. in the kernel. Loading Loading
Documentation/block/switching-sched.txt 0 → 100644 +22 −0 Original line number Original line Diff line number Diff line As of the Linux 2.6.10 kernel, it is now possible to change the IO scheduler for a given block device on the fly (thus making it possible, for instance, to set the CFQ scheduler for the system default, but set a specific device to use the anticipatory or noop schedulers - which can improve that device's throughput). To set a specific scheduler, simply do this: echo SCHEDNAME > /sys/block/DEV/queue/scheduler where SCHEDNAME is the name of a defined IO scheduler, and DEV is the device name (hda, hdb, sga, or whatever you happen to have). The list of defined schedulers can be found by simply doing a "cat /sys/block/DEV/queue/scheduler" - the list of valid names will be displayed, with the currently selected scheduler in brackets: # cat /sys/block/hda/queue/scheduler noop anticipatory deadline [cfq] # echo anticipatory > /sys/block/hda/queue/scheduler # cat /sys/block/hda/queue/scheduler noop [anticipatory] deadline cfq
Documentation/cpu-freq/index.txt +1 −1 Original line number Original line Diff line number Diff line Loading @@ -53,4 +53,4 @@ the CPUFreq Mailing list: * http://lists.linux.org.uk/mailman/listinfo/cpufreq * http://lists.linux.org.uk/mailman/listinfo/cpufreq Clock and voltage scaling for the SA-1100: Clock and voltage scaling for the SA-1100: * http://www.lart.tudelft.nl/projects/scaling * http://www.lartmaker.nl/projects/scaling
Documentation/feature-removal-schedule.txt +3 −2 Original line number Original line Diff line number Diff line Loading @@ -25,8 +25,9 @@ Who: Adrian Bunk <bunk@stusta.de> --------------------------- --------------------------- What: drivers depending on OBSOLETE_OSS_DRIVER What: drivers that were depending on OBSOLETE_OSS_DRIVER When: January 2006 (config options already removed) When: before 2.6.19 Why: OSS drivers with ALSA replacements Why: OSS drivers with ALSA replacements Who: Adrian Bunk <bunk@stusta.de> Who: Adrian Bunk <bunk@stusta.de> Loading
Documentation/filesystems/sysfs.txt +5 −0 Original line number Original line Diff line number Diff line Loading @@ -246,6 +246,7 @@ class/ devices/ devices/ firmware/ firmware/ net/ net/ fs/ devices/ contains a filesystem representation of the device tree. It maps devices/ contains a filesystem representation of the device tree. It maps directly to the internal kernel device tree, which is a hierarchy of directly to the internal kernel device tree, which is a hierarchy of Loading @@ -264,6 +265,10 @@ drivers/ contains a directory for each device driver that is loaded for devices on that particular bus (this assumes that drivers do not for devices on that particular bus (this assumes that drivers do not span multiple bus types). span multiple bus types). fs/ contains a directory for some filesystems. Currently each filesystem wanting to export attributes must create its own hierarchy below fs/ (see ./fuse.txt for an example). More information can driver-model specific features can be found in More information can driver-model specific features can be found in Documentation/driver-model/. Documentation/driver-model/. Loading
Documentation/vm/hugetlbpage.txt +10 −1 Original line number Original line Diff line number Diff line Loading @@ -32,7 +32,16 @@ The output of "cat /proc/meminfo" will have lines like: ..... ..... HugePages_Total: xxx HugePages_Total: xxx HugePages_Free: yyy HugePages_Free: yyy Hugepagesize: zzz KB HugePages_Rsvd: www Hugepagesize: zzz kB where: HugePages_Total is the size of the pool of hugepages. HugePages_Free is the number of hugepages in the pool that are not yet allocated. HugePages_Rsvd is short for "reserved," and is the number of hugepages for which a commitment to allocate from the pool has been made, but no allocation has yet been made. It's vaguely analogous to overcommit. /proc/filesystems should also show a filesystem of type "hugetlbfs" configured /proc/filesystems should also show a filesystem of type "hugetlbfs" configured in the kernel. in the kernel. Loading