Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel
os
linux
gfp: gfp_types.h: fix typos & punctuation
Correct typos/spellos and punctutation.
Link: https://lkml.kernel.org/r/20231213043316.10128-1-rdunlap@infradead.org
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
authored by
Randy Dunlap
and committed by
Andrew Morton
0abfa8ef
e93b81a3
+6
-6
+6
-6
include/linux/gfp_types.h
+6
-6
include/linux/gfp_types.h
···
162
162
* %__GFP_RECLAIM is shorthand to allow/forbid both direct and kswapd reclaim.
163
163
*
164
164
* The default allocator behavior depends on the request size. We have a concept
165
-
* of so called costly allocations (with order > %PAGE_ALLOC_COSTLY_ORDER).
165
+
* of so-called costly allocations (with order > %PAGE_ALLOC_COSTLY_ORDER).
166
166
* !costly allocations are too essential to fail so they are implicitly
167
167
* non-failing by default (with some exceptions like OOM victims might fail so
168
168
* the caller still has to check for failures) while costly requests try to be
169
169
* not disruptive and back off even without invoking the OOM killer.
170
170
* The following three modifiers might be used to override some of these
171
-
* implicit rules
171
+
* implicit rules.
172
172
*
173
173
* %__GFP_NORETRY: The VM implementation will try only very lightweight
174
174
* memory direct reclaim to get some memory under memory pressure (thus
175
175
* it can sleep). It will avoid disruptive actions like OOM killer. The
176
176
* caller must handle the failure which is quite likely to happen under
177
177
* heavy memory pressure. The flag is suitable when failure can easily be
178
-
* handled at small cost, such as reduced throughput
178
+
* handled at small cost, such as reduced throughput.
179
179
*
180
180
* %__GFP_RETRY_MAYFAIL: The VM implementation will retry memory reclaim
181
181
* procedures that have previously failed if there is some indication
182
-
* that progress has been made else where. It can wait for other
183
-
* tasks to attempt high level approaches to freeing memory such as
182
+
* that progress has been made elsewhere. It can wait for other
183
+
* tasks to attempt high-level approaches to freeing memory such as
184
184
* compaction (which removes fragmentation) and page-out.
185
185
* There is still a definite limit to the number of retries, but it is
186
186
* a larger limit than with %__GFP_NORETRY.
···
230
230
* is being zeroed (either via __GFP_ZERO or via init_on_alloc, provided that
231
231
* __GFP_SKIP_ZERO is not set). This flag is intended for optimization: setting
232
232
* memory tags at the same time as zeroing memory has minimal additional
233
-
* performace impact.
233
+
* performance impact.
234
234
*
235
235
* %__GFP_SKIP_KASAN makes KASAN skip unpoisoning on page allocation.
236
236
* Used for userspace and vmalloc pages; the latter are unpoisoned by