Loading Documentation/ABI/obsolete/proc-pid-oom_adj 0 → 100644 +22 −0 Original line number Diff line number Diff line What: /proc/<pid>/oom_adj When: August 2012 Why: /proc/<pid>/oom_adj allows userspace to influence the oom killer's badness heuristic used to determine which task to kill when the kernel is out of memory. The badness heuristic has since been rewritten since the introduction of this tunable such that its meaning is deprecated. The value was implemented as a bitshift on a score generated by the badness() function that did not have any precise units of measure. With the rewrite, the score is given as a proportion of available memory to the task allocating pages, so using a bitshift which grows the score exponentially is, thus, impossible to tune with fine granularity. A much more powerful interface, /proc/<pid>/oom_score_adj, was introduced with the oom killer rewrite that allows users to increase or decrease the badness() score linearly. This interface will replace /proc/<pid>/oom_adj. A warning will be emitted to the kernel log if an application uses this deprecated interface. After it is printed once, future warnings will be suppressed until the kernel is rebooted. Documentation/arm/OMAP/DSS +4 −3 Original line number Diff line number Diff line Loading @@ -255,9 +255,10 @@ framebuffer parameters. Kernel boot arguments --------------------- vram=<size> - Amount of total VRAM to preallocate. For example, "10M". omapfb allocates memory for framebuffers from VRAM. vram=<size>[,<physaddr>] - Amount of total VRAM to preallocate and optionally a physical start memory address. For example, "10M". omapfb allocates memory for framebuffers from VRAM. omapfb.mode=<display>:<mode>[,...] - Default video mode for specified displays. For example, Loading Documentation/block/switching-sched.txt +4 −4 Original line number Diff line number Diff line Loading @@ -16,7 +16,7 @@ you can do so by typing: 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 set a specific device to use the deadline or noop schedulers - which can improve that device's throughput). To set a specific scheduler, simply do this: Loading @@ -31,7 +31,7 @@ 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 noop deadline [cfq] # echo deadline > /sys/block/hda/queue/scheduler # cat /sys/block/hda/queue/scheduler noop [anticipatory] deadline cfq noop [deadline] cfq Documentation/feature-removal-schedule.txt +10 −0 Original line number Diff line number Diff line Loading @@ -554,3 +554,13 @@ Why: This is a legacy interface which have been replaced by a more Who: NeilBrown <neilb@suse.de> ---------------------------- What: i2c_adapter.id When: June 2011 Why: This field is deprecated. I2C device drivers shouldn't change their behavior based on the underlying I2C adapter. Instead, the I2C adapter driver should instantiate the I2C devices and provide the needed platform-specific information. Who: Jean Delvare <khali@linux-fr.org> ---------------------------- Documentation/filesystems/xfs-delayed-logging-design.txt +0 −11 Original line number Diff line number Diff line Loading @@ -794,17 +794,6 @@ designed. Roadmap: 2.6.37 Remove experimental tag from mount option => should be roughly 6 months after initial merge => enough time to: => gain confidence and fix problems reported by early adopters (a.k.a. guinea pigs) => address worst performance regressions and undesired behaviours => start tuning/optimising code for parallelism => start tuning/optimising algorithms consuming excessive CPU time 2.6.39 Switch default mount option to use delayed logging => should be roughly 12 months after initial merge => enough time to shake out remaining problems before next round of Loading Loading
Documentation/ABI/obsolete/proc-pid-oom_adj 0 → 100644 +22 −0 Original line number Diff line number Diff line What: /proc/<pid>/oom_adj When: August 2012 Why: /proc/<pid>/oom_adj allows userspace to influence the oom killer's badness heuristic used to determine which task to kill when the kernel is out of memory. The badness heuristic has since been rewritten since the introduction of this tunable such that its meaning is deprecated. The value was implemented as a bitshift on a score generated by the badness() function that did not have any precise units of measure. With the rewrite, the score is given as a proportion of available memory to the task allocating pages, so using a bitshift which grows the score exponentially is, thus, impossible to tune with fine granularity. A much more powerful interface, /proc/<pid>/oom_score_adj, was introduced with the oom killer rewrite that allows users to increase or decrease the badness() score linearly. This interface will replace /proc/<pid>/oom_adj. A warning will be emitted to the kernel log if an application uses this deprecated interface. After it is printed once, future warnings will be suppressed until the kernel is rebooted.
Documentation/arm/OMAP/DSS +4 −3 Original line number Diff line number Diff line Loading @@ -255,9 +255,10 @@ framebuffer parameters. Kernel boot arguments --------------------- vram=<size> - Amount of total VRAM to preallocate. For example, "10M". omapfb allocates memory for framebuffers from VRAM. vram=<size>[,<physaddr>] - Amount of total VRAM to preallocate and optionally a physical start memory address. For example, "10M". omapfb allocates memory for framebuffers from VRAM. omapfb.mode=<display>:<mode>[,...] - Default video mode for specified displays. For example, Loading
Documentation/block/switching-sched.txt +4 −4 Original line number Diff line number Diff line Loading @@ -16,7 +16,7 @@ you can do so by typing: 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 set a specific device to use the deadline or noop schedulers - which can improve that device's throughput). To set a specific scheduler, simply do this: Loading @@ -31,7 +31,7 @@ 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 noop deadline [cfq] # echo deadline > /sys/block/hda/queue/scheduler # cat /sys/block/hda/queue/scheduler noop [anticipatory] deadline cfq noop [deadline] cfq
Documentation/feature-removal-schedule.txt +10 −0 Original line number Diff line number Diff line Loading @@ -554,3 +554,13 @@ Why: This is a legacy interface which have been replaced by a more Who: NeilBrown <neilb@suse.de> ---------------------------- What: i2c_adapter.id When: June 2011 Why: This field is deprecated. I2C device drivers shouldn't change their behavior based on the underlying I2C adapter. Instead, the I2C adapter driver should instantiate the I2C devices and provide the needed platform-specific information. Who: Jean Delvare <khali@linux-fr.org> ----------------------------
Documentation/filesystems/xfs-delayed-logging-design.txt +0 −11 Original line number Diff line number Diff line Loading @@ -794,17 +794,6 @@ designed. Roadmap: 2.6.37 Remove experimental tag from mount option => should be roughly 6 months after initial merge => enough time to: => gain confidence and fix problems reported by early adopters (a.k.a. guinea pigs) => address worst performance regressions and undesired behaviours => start tuning/optimising code for parallelism => start tuning/optimising algorithms consuming excessive CPU time 2.6.39 Switch default mount option to use delayed logging => should be roughly 12 months after initial merge => enough time to shake out remaining problems before next round of Loading
