aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/event_analyzing_sample.py
diff options
context:
space:
mode:
authorMichal Hocko <[email protected]>2020-06-03 15:56:49 -0700
committerLinus Torvalds <[email protected]>2020-06-03 20:09:43 -0700
commit574c1ae66c12410a08aeef8474936baa50e0371d (patch)
tree0380ac43d2e361fc1fcfc7e6b6ffdd637fab1589 /tools/perf/scripts/python/event_analyzing_sample.py
parent47227d27e2fcb01a9e8f5958d8997cf47a820afc (diff)
mm: clarify __GFP_MEMALLOC usage
It seems that the existing documentation is not explicit about the expected usage and potential risks enough. While it is calls out that users have to free memory when using this flag it is not really apparent that users have to careful to not deplete memory reserves and that they should implement some sort of throttling wrt. freeing process. This is partly based on Neil's explanation [1]. Let's also call out that a pre allocated pool allocator should be considered. [1] http://lkml.kernel.org/r/[email protected] [[email protected]: coding style fixes] [[email protected]: update] Link: http://lkml.kernel.org/r/[email protected] Signed-off-by: Michal Hocko <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Cc: David Rientjes <[email protected]> Cc: Joel Fernandes <[email protected]> Cc: Neil Brown <[email protected]> Cc: Paul E. McKenney <[email protected]> Cc: John Hubbard <[email protected]> Link: http://lkml.kernel.org/r/[email protected] Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions