tjh.dev
Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel
os
linux
Documentation: fix the VM knobs descritpion WRT pdflush
The pdflush thread is long gone, however we still mention it incorrectly in the
kernel documentation. This patch fixes the situation.
Cc: Randy Dunlap <rdunlap@xenotime.net>
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
authored by
Artem Bityutskiy
and committed by
Al Viro
6601fac8
34e5053f
+13
-13
+6
-6
Documentation/laptops/laptop-mode.txt
+6
-6
Documentation/laptops/laptop-mode.txt
···
262
262
263
263
#
264
264
# Allowed dirty background ratio, in percent. Once DIRTY_RATIO has been
265
-
# exceeded, the kernel will wake pdflush which will then reduce the amount
266
-
# of dirty memory to dirty_background_ratio. Set this nice and low, so once
267
-
# some writeout has commenced, we do a lot of it.
265
+
# exceeded, the kernel will wake flusher threads which will then reduce the
266
+
# amount of dirty memory to dirty_background_ratio. Set this nice and low,
267
+
# so once some writeout has commenced, we do a lot of it.
268
268
#
269
269
#DIRTY_BACKGROUND_RATIO=5
270
270
···
384
384
385
385
#
386
386
# Allowed dirty background ratio, in percent. Once DIRTY_RATIO has been
387
-
# exceeded, the kernel will wake pdflush which will then reduce the amount
388
-
# of dirty memory to dirty_background_ratio. Set this nice and low, so once
389
-
# some writeout has commenced, we do a lot of it.
387
+
# exceeded, the kernel will wake flusher threads which will then reduce the
388
+
# amount of dirty memory to dirty_background_ratio. Set this nice and low,
389
+
# so once some writeout has commenced, we do a lot of it.
390
390
#
391
391
DIRTY_BACKGROUND_RATIO=${DIRTY_BACKGROUND_RATIO:-'5'}
392
392
+7
-7
Documentation/sysctl/vm.txt
+7
-7
Documentation/sysctl/vm.txt
···
76
76
77
77
dirty_background_bytes
78
78
79
-
Contains the amount of dirty memory at which the pdflush background writeback
80
-
daemon will start writeback.
79
+
Contains the amount of dirty memory at which the background kernel
80
+
flusher threads will start writeback.
81
81
82
82
Note: dirty_background_bytes is the counterpart of dirty_background_ratio. Only
83
83
one of them may be specified at a time. When one sysctl is written it is
···
89
89
dirty_background_ratio
90
90
91
91
Contains, as a percentage of total system memory, the number of pages at which
92
-
the pdflush background writeback daemon will start writing out dirty data.
92
+
the background kernel flusher threads will start writing out dirty data.
93
93
94
94
==============================================================
95
95
···
112
112
dirty_expire_centisecs
113
113
114
114
This tunable is used to define when dirty data is old enough to be eligible
115
-
for writeout by the pdflush daemons. It is expressed in 100'ths of a second.
116
-
Data which has been dirty in-memory for longer than this interval will be
117
-
written out next time a pdflush daemon wakes up.
115
+
for writeout by the kernel flusher threads. It is expressed in 100'ths
116
+
of a second. Data which has been dirty in-memory for longer than this
117
+
interval will be written out next time a flusher thread wakes up.
118
118
119
119
==============================================================
120
120
···
128
128
129
129
dirty_writeback_centisecs
130
130
131
-
The pdflush writeback daemons will periodically wake up and write `old' data
131
+
The kernel flusher threads will periodically wake up and write `old' data
132
132
out to disk. This tunable expresses the interval between those wakeups, in
133
133
100'ths of a second.
134
134