diff options
author | Rasmus Villemoes <[email protected]> | 2018-02-21 14:45:43 -0800 |
---|---|---|
committer | Linus Torvalds <[email protected]> | 2018-02-21 15:35:43 -0800 |
commit | b1a8a7a70043400d1e685899548c92b92f640d71 (patch) | |
tree | 4295e3cb0440b43ad6a2b95a777b4bccb858bdb6 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | 7ba716698cc53f8d5367766c93c538c7da6c68ce (diff) |
ida: do zeroing in ida_pre_get()
As far as I can tell, the only place the per-cpu ida_bitmap is populated
is in ida_pre_get. The pre-allocated element is stolen in two places in
ida_get_new_above, in both cases immediately followed by a memset(0).
Since ida_get_new_above is called with locks held, do the zeroing in
ida_pre_get, or rather let kmalloc() do it. Also, apparently gcc
generates ~44 bytes of code to do a memset(, 0, 128):
$ scripts/bloat-o-meter vmlinux.{0,1}
add/remove: 0/0 grow/shrink: 2/1 up/down: 5/-88 (-83)
Function old new delta
ida_pre_get 115 119 +4
vermagic 27 28 +1
ida_get_new_above 715 627 -88
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Rasmus Villemoes <[email protected]>
Acked-by: Matthew Wilcox <[email protected]>
Cc: Eric Biggers <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions