From: Minchan Kim <minchan@kernel.org>
To: "Arve Hjønnevåg" <arve@android.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Todd Kjos <tkjos@google.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Martijn Coenen <maco@android.com>
Subject: Re: [PATCH v2] ANDROID: binder: change down_write to down_read
Date: Thu, 29 Mar 2018 11:01:51 +0900 [thread overview]
Message-ID: <20180329020151.GA91696@rodete-desktop-imager.corp.google.com> (raw)
In-Reply-To: <CAMP5Xge2bFr2d9zss_Qi49RE7NsRTQpA0q7s_uwmMw4x3_ceug@mail.gmail.com>
On Wed, Mar 28, 2018 at 06:59:41PM -0700, Arve Hjønnevåg wrote:
> On Wed, Mar 28, 2018 at 6:00 PM, Minchan Kim <minchan@kernel.org> wrote:
> > binder_update_page_range needs down_write of mmap_sem because
> > vm_insert_page need to change vma->vm_flags to VM_MIXEDMAP unless
> > it is set. However, when I profile binder working, it seems
> > every binder buffers should be mapped in advance by binder_mmap.
> > It means we could set VM_MIXEDMAP in bider_mmap time which is
> > already hold a mmap_sem as down_write so binder_update_page_range
> > doesn't need to hold a mmap_sem as down_write.
> >
> > Android suffers from mmap_sem contention so let's reduce mmap_sem
> > down_write.
> >
> > Cc: Todd Kjos <tkjos@google.com>
> > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Reviewed-by: Martijn Coenen <maco@android.com>
> > Signed-off-by: Minchan Kim <minchan@kernel.org>
> > ---
> > From v1:
> > * remove WARN_ON_ONCE - Greg
> > * add reviewed-by - Martijn
> >
> > Martijn, I took your LGTM of v1 as Reviewed-by. If you don't like it
> > or want to change it to acked-by, please, tell me.
> >
> > drivers/android/binder.c | 2 +-
> > drivers/android/binder_alloc.c | 6 +++---
> > 2 files changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/android/binder.c b/drivers/android/binder.c
> > index 764b63a5aade..9a14c6dd60c4 100644
> > --- a/drivers/android/binder.c
> > +++ b/drivers/android/binder.c
> > @@ -4722,7 +4722,7 @@ static int binder_mmap(struct file *filp, struct vm_area_struct *vma)
> > failure_string = "bad vm_flags";
> > goto err_bad_arg;
> > }
> > - vma->vm_flags = (vma->vm_flags | VM_DONTCOPY) & ~VM_MAYWRITE;
> > + vma->vm_flags |= (VM_DONTCOPY | VM_MIXEDMAP) & ~VM_MAYWRITE;
>
> Why did you change this to |=? You are no longer clearing VM_MAYWRITE.
Oops, Thanks for pointing out.
I will respin.
prev parent reply other threads:[~2018-03-29 2:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 1:00 Minchan Kim
2018-03-29 1:59 ` Arve Hjønnevåg
2018-03-29 2:01 ` Minchan Kim [this message]
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=20180329020151.GA91696@rodete-desktop-imager.corp.google.com \
--to=minchan@kernel.org \
--cc=arve@android.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=tkjos@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
all inboxes | Powered by JetHome®