Loading Documentation/HOWTO +2 −1 Original line number Diff line number Diff line Loading @@ -603,7 +603,8 @@ start exactly where you are now. ---------- Thanks to Paolo Ciarrocchi who allowed the "Development Process" section Thanks to Paolo Ciarrocchi who allowed the "Development Process" (http://linux.tar.bz/articles/2.6-development_process) section to be based on text he had written, and to Randy Dunlap and Gerrit Huizenga for some of the list of things you should and should not say. Also thanks to Pat Mochel, Hanna Linder, Randy Dunlap, Kay Sievers, Loading Documentation/block/switching-sched.txt 0 → 100644 +22 −0 Original line number 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 Diff line number Diff line Loading @@ -53,4 +53,4 @@ the CPUFreq Mailing list: * http://lists.linux.org.uk/mailman/listinfo/cpufreq 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 Diff line number Diff line Loading @@ -25,8 +25,9 @@ Who: Adrian Bunk <bunk@stusta.de> --------------------------- What: drivers depending on OBSOLETE_OSS_DRIVER When: January 2006 What: drivers that were depending on OBSOLETE_OSS_DRIVER (config options already removed) When: before 2.6.19 Why: OSS drivers with ALSA replacements Who: Adrian Bunk <bunk@stusta.de> Loading Documentation/filesystems/sysfs.txt +5 −0 Original line number Diff line number Diff line Loading @@ -246,6 +246,7 @@ class/ devices/ firmware/ net/ fs/ devices/ contains a filesystem representation of the device tree. It maps 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 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 Documentation/driver-model/. Loading Loading
Documentation/HOWTO +2 −1 Original line number Diff line number Diff line Loading @@ -603,7 +603,8 @@ start exactly where you are now. ---------- Thanks to Paolo Ciarrocchi who allowed the "Development Process" section Thanks to Paolo Ciarrocchi who allowed the "Development Process" (http://linux.tar.bz/articles/2.6-development_process) section to be based on text he had written, and to Randy Dunlap and Gerrit Huizenga for some of the list of things you should and should not say. Also thanks to Pat Mochel, Hanna Linder, Randy Dunlap, Kay Sievers, Loading
Documentation/block/switching-sched.txt 0 → 100644 +22 −0 Original line number 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 Diff line number Diff line Loading @@ -53,4 +53,4 @@ the CPUFreq Mailing list: * http://lists.linux.org.uk/mailman/listinfo/cpufreq 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 Diff line number Diff line Loading @@ -25,8 +25,9 @@ Who: Adrian Bunk <bunk@stusta.de> --------------------------- What: drivers depending on OBSOLETE_OSS_DRIVER When: January 2006 What: drivers that were depending on OBSOLETE_OSS_DRIVER (config options already removed) When: before 2.6.19 Why: OSS drivers with ALSA replacements Who: Adrian Bunk <bunk@stusta.de> Loading
Documentation/filesystems/sysfs.txt +5 −0 Original line number Diff line number Diff line Loading @@ -246,6 +246,7 @@ class/ devices/ firmware/ net/ fs/ devices/ contains a filesystem representation of the device tree. It maps 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 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 Documentation/driver-model/. Loading