vm: avoid using find_vma_prev() unnecessarily
authorLinus Torvalds <torvalds@linux-foundation.org>
Wed, 7 Mar 2012 02:23:36 +0000 (18:23 -0800)
committerLinus Torvalds <torvalds@linux-foundation.org>
Wed, 7 Mar 2012 02:23:36 +0000 (18:23 -0800)
commit097d59106a8e4b42d07c9892fdd7790f1659c6ff
treebabf61a0287b0f09f80580847274877831ed6869
parent71fece9511717750d86691e0f517ad04f3c8a801
vm: avoid using find_vma_prev() unnecessarily

Several users of "find_vma_prev()" were not in fact interested in the
previous vma if there was no primary vma to be found either.  And in
those cases, we're much better off just using the regular "find_vma()",
and then "prev" can be looked up by just checking vma->vm_prev.

The find_vma_prev() semantics are fairly subtle (see Mikulas' recent
commit 83cd904d271b: "mm: fix find_vma_prev"), and the whole "return
prev by reference" means that it generates worse code too.

Thus this "let's avoid using this inconvenient and clearly too subtle
interface when we don't really have to" patch.

Cc: Mikulas Patocka <mpatocka@redhat.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
arch/x86/mm/hugetlbpage.c
mm/mempolicy.c
mm/mlock.c
mm/mprotect.c