From: David Hildenbrand <david@redhat.com>
To: linmiaohe <linmiaohe@huawei.com>,
akpm@linux-foundation.org, richardw.yang@linux.intel.com,
sfr@canb.auug.org.au, rppt@linux.ibm.com, jannh@google.com,
steve.capper@arm.com, catalin.marinas@arm.com,
aarcange@redhat.com, chenjianhong2@huawei.com, walken@google.com,
dave.hansen@linux.intel.com, tiny.windzz@gmail.com,
jhubbard@nvidia.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] mm: get rid of odd jump labels in find_mergeable_anon_vma()
Date: Mon, 18 Nov 2019 10:45:10 +0100 [thread overview]
Message-ID: <8b5f515f-307b-1e73-249f-f69a4b8c4318@redhat.com> (raw)
In-Reply-To: <1574059147-13678-1-git-send-email-linmiaohe@huawei.com>
On 18.11.19 07:39, linmiaohe wrote:
> From: Miaohe Lin <linmiaohe@huawei.com>
>
> The jump labels try_prev and none are not really needed
> in find_mergeable_anon_vma(), eliminate them to improve
> readability.
>
> Reviewed-by: David Hildenbrand <david@redhat.com>
> Reviewed-by: John Hubbard <jhubbard@nvidia.com>
> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
> ---
> -v2:
> Fix commit descriptions and further simplify the code
> as suggested by David Hildenbrand and John Hubbard.
> -v3:
> Rewrite patch version info. Don't show this in commit log.
> ---
> mm/mmap.c | 27 +++++++++++++--------------
> 1 file changed, 13 insertions(+), 14 deletions(-)
>
> diff --git a/mm/mmap.c b/mm/mmap.c
> index 4d4db76a07da..ff02c23fd375 100644
> --- a/mm/mmap.c
> +++ b/mm/mmap.c
> @@ -1276,26 +1276,25 @@ static struct anon_vma *reusable_anon_vma(struct vm_area_struct *old, struct vm_
> */
> struct anon_vma *find_mergeable_anon_vma(struct vm_area_struct *vma)
> {
> - struct anon_vma *anon_vma;
> + struct anon_vma *anon_vma = NULL;
> struct vm_area_struct *near;
>
> + /* Try next first. */
> near = vma->vm_next;
> - if (!near)
> - goto try_prev;
> + if (near) {
> + anon_vma = reusable_anon_vma(near, vma, near);
> + if (anon_vma)
> + return anon_vma;
> + }
I think you can get rid of near completely as well
if (vma->vm_next) {
anon_vma = reusable_anon_vma(near, vma, vma->vm_next);
if (anon_vma)
return anon_vma;
}
...
Apart from that looks good to me.
>
> - anon_vma = reusable_anon_vma(near, vma, near);
> - if (anon_vma)
> - return anon_vma;
> -try_prev:
> + /* Try prev next. */
> near = vma->vm_prev;
> - if (!near)
> - goto none;
> + if (near)
> + anon_vma = reusable_anon_vma(near, near, vma);
>
> - anon_vma = reusable_anon_vma(near, near, vma);
> - if (anon_vma)
> - return anon_vma;
> -none:
> /*
> + * We might reach here with anon_vma == NULL if we can't find
> + * any reusable anon_vma.
> * There's no absolute need to look only at touching neighbours:
> * we could search further afield for "compatible" anon_vmas.
> * But it would probably just be a waste of time searching,
> @@ -1303,7 +1302,7 @@ struct anon_vma *find_mergeable_anon_vma(struct vm_area_struct *vma)
> * We're trying to allow mprotect remerging later on,
> * not trying to minimize memory used for anon_vmas.
> */
> - return NULL;
> + return anon_vma;
> }
>
> /*
>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2019-11-18 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 6:39 linmiaohe
2019-11-18 9:45 ` David Hildenbrand [this message]
2019-11-18 11:31 linmiaohe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8b5f515f-307b-1e73-249f-f69a4b8c4318@redhat.com \
--to=david@redhat.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=chenjianhong2@huawei.com \
--cc=dave.hansen@linux.intel.com \
--cc=jannh@google.com \
--cc=jhubbard@nvidia.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=richardw.yang@linux.intel.com \
--cc=rppt@linux.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=steve.capper@arm.com \
--cc=tiny.windzz@gmail.com \
--cc=walken@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox