diff options
| author | Doug Ledford <[email protected]> | 2018-09-21 11:30:12 -0400 |
|---|---|---|
| committer | Jason Gunthorpe <[email protected]> | 2018-09-25 15:19:06 -0600 |
| commit | 3312d1c6bdee6aa912c099c0ac0662d197c52842 (patch) | |
| tree | 97a27e26c26602a973a30d6c964eb0c17319873a /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | 1b571086e869395b6a11ab24186b0104fe05c057 (diff) | |
RDMA/umem: Minor optimizations
Noticed while reviewing commit d4b4dd1b9706 ("RDMA/umem: Do not use
current->tgid to track the mm_struct") patch. Why would we take a lock,
adjust a protected variable, drop the lock, and *then* check the input
into our protected variable adjustment? Then we have to take the lock
again on our error unwind. Let's just check the input early and skip
taking the locks needlessly if the input isn't valid.
It was also noticed that we set mm = current->mm, we then never modify
mm, but we still go back and reference current->mm a number of times
needlessly. Be consistent in using the stored reference in mm.
Signed-off-by: Doug Ledford <[email protected]>
Reviewed-by: Leon Romanovsky <[email protected]>
Signed-off-by: Jason Gunthorpe <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions