summaryrefslogtreecommitdiffstats
path: root/Documentation/core-api
diff options
context:
space:
mode:
authorJonathan Corbet <corbet@lwn.net>2018-05-29 13:44:58 +0200
committerJonathan Corbet <corbet@lwn.net>2018-05-29 14:45:55 +0200
commitd43f2c98f63a961172172ce4d1b3aeea7fbc0628 (patch)
tree6bb19fc59cb6999945babfb32e8205919349c75d /Documentation/core-api
parentdoc: document scope NOFS, NOIO APIs (diff)
downloadlinux-d43f2c98f63a961172172ce4d1b3aeea7fbc0628.tar.xz
linux-d43f2c98f63a961172172ce4d1b3aeea7fbc0628.zip
docs: Use the kerneldoc comments for memalloc_no*()
Now that we have kerneldoc comments for memalloc_no{fs,io}_{save_restore}(), go ahead and pull them into the docs. Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/core-api')
-rw-r--r--Documentation/core-api/gfp_mask-from-fs-io.rst5
1 files changed, 5 insertions, 0 deletions
diff --git a/Documentation/core-api/gfp_mask-from-fs-io.rst b/Documentation/core-api/gfp_mask-from-fs-io.rst
index 2dc442b04a77..e0df8f416582 100644
--- a/Documentation/core-api/gfp_mask-from-fs-io.rst
+++ b/Documentation/core-api/gfp_mask-from-fs-io.rst
@@ -33,6 +33,11 @@ section from a filesystem or I/O point of view. Any allocation from that
scope will inherently drop __GFP_FS respectively __GFP_IO from the given
mask so no memory allocation can recurse back in the FS/IO.
+.. kernel-doc:: include/linux/sched/mm.h
+ :functions: memalloc_nofs_save memalloc_nofs_restore
+.. kernel-doc:: include/linux/sched/mm.h
+ :functions: memalloc_noio_save memalloc_noio_restore
+
FS/IO code then simply calls the appropriate save function before
any critical section with respect to the reclaim is started - e.g.
lock shared with the reclaim context or when a transaction context