LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Suren Baghdasaryan <surenb@google.com>
To: Michal Hocko <mhocko@suse.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	David Rientjes <rientjes@google.com>,
	Matthew Wilcox <willy@infradead.org>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Roman Gushchin <guro@fb.com>, Rik van Riel <riel@surriel.com>,
	Minchan Kim <minchan@kernel.org>,
	Christian Brauner <christian@brauner.io>,
	Christoph Hellwig <hch@infradead.org>,
	Oleg Nesterov <oleg@redhat.com>,
	David Hildenbrand <david@redhat.com>,
	Jann Horn <jannh@google.com>, Shakeel Butt <shakeelb@google.com>,
	Andy Lutomirski <luto@kernel.org>,
	Christian Brauner <christian.brauner@ubuntu.com>,
	Florian Weimer <fweimer@redhat.com>,
	Jan Engelhardt <jengelh@inai.de>,
	Tim Murray <timmurray@google.com>,
	Linux API <linux-api@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	kernel-team <kernel-team@android.com>
Subject: Re: [PATCH v7 1/2] mm: introduce process_mrelease system call
Date: Sun, 8 Aug 2021 09:13:30 -0700	[thread overview]
Message-ID: <CAJuCfpFeup+rppM7mbJWJeaCbTdbp=1=r24CjmLWWv4Vsydd2A@mail.gmail.com> (raw)
In-Reply-To: <CAJuCfpFL_7Zk4Nk5E_kCSnsCsXgmWGW9R3AnXW-T5EH7URUkRg@mail.gmail.com>

On Fri, Aug 6, 2021 at 9:07 AM Suren Baghdasaryan <surenb@google.com> wrote:
>
> On Thu, Aug 5, 2021 at 11:40 PM Michal Hocko <mhocko@suse.com> wrote:
> >
> > On Thu 05-08-21 10:08:58, Suren Baghdasaryan wrote:
> > [...]
> > > +     /*
> > > +      * If the task is dying and in the process of releasing its memory
> > > +      * then get its mm.
> > > +      */
> > > +     p = find_lock_task_mm(task);
> > > +     if (!p) {
> > > +             ret = -ESRCH;
> > > +             goto put_pid;
> > > +     }
> > > +     if (task != p) {
> > > +             get_task_struct(p);
> > > +             put_task_struct(task);
> > > +             task = p;
> > > +     }
> >
> > Why do you need to take a reference to the p here? You are under
> > task_lock so this will not go away and you only need p to get your mm.
>
> True.
>
> >
> > > +
> > > +     /* If the work has been done already, just exit with success */
> > > +     if (test_bit(MMF_OOM_SKIP, &task->mm->flags))
> > > +             goto put_task;
> >
> > You want to release the task_lock
>
> Missed it again :(
>
> >
> > > +
> > > +     if (task_will_free_mem(task) && (task->flags & PF_KTHREAD) == 0) {
> >
> > you want task_will_free_mem(p) and what is the point of the PF_KTHREAD
> > check?
>
> Yeah, looks like task_will_free_mem() covers that case already.
>
> >
> > > +             mm = task->mm;
> > > +             mmget(mm);
> >
> > All you need is to make sure mm will not get released under your feet
> > once task_lock is released so mmgrab is the right thing to do here. The
> > address space can be torn down in parallel and that is OK and desirable.
> >
> > I think you really want something like this:
> >
> >         if (flags)
> >                 return -EINVAL;
> >
> >         pid = pidfd_get_pid(fd, &f_flags);
> >         if (IS_ERR(pid))
> >                 return PTR_ERR(pid);
> >         task = get_pid_task(pid, PIDTYPE_PID);
> >         if (!task) {
> >                 ret = -ESRCH;
> >                 goto put_pid;
> >         }
> >
> >         /*
> >          * Make sure to chose a thread which still has a reference to mm
> >          * during the group exit
> >          */
> >         p = find_lock_task_mm(task);
> >         if (!p) {
> >                 ret = -ESRCH;
> >                 goto put_task;
> >         }
> >
> >         mm = task->mm;
> >         mmgrab(mm);
> >         reap = true;
> >         /* If the work has been done already, just exit with success */
> >         if (test_bit(MMF_OOM_SKIP, &mm->flags)) {
> >                 reap = false;
> >         } else if (!task_will_free_mem(p)) {
> >                 reap = false;
> >                 ret = -EINVAL;
> >         }
> >         task_unlock(p);
> >
> >         if (!reap)
> >                 goto dropmm;;
> >
> >         /* Do the work*/
> >
> >
> > dropmm:
> >         mmdrop(mm);
> > put_task:
> >         put_task(task);
> > put_pid:
> >         put_pid(pid);
> >
> >         return ret;
> >
>
> This is indeed simpler to follow. I'll adopt your version. Thanks!

v8 is posted at https://lore.kernel.org/patchwork/patch/1473697/
Testing shows performance improvement from replacing mmget with mmgrab.

>
> > --
> > Michal Hocko
> > SUSE Labs

      reply	other threads:[~2021-08-08 16:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-05 17:08 Suren Baghdasaryan
2021-08-05 17:08 ` [PATCH v7 2/2] mm: wire up syscall process_mrelease Suren Baghdasaryan
2021-08-05 17:29 ` [PATCH v7 1/2] mm: introduce process_mrelease system call David Hildenbrand
2021-08-05 17:49   ` Suren Baghdasaryan
2021-08-05 17:55     ` David Hildenbrand
2021-08-05 17:56     ` Shakeel Butt
2021-08-05 18:37       ` Suren Baghdasaryan
2021-08-06  6:41         ` Michal Hocko
2021-08-06  6:40 ` Michal Hocko
2021-08-06  9:23   ` Shakeel Butt
2021-08-06 10:15     ` Michal Hocko
2021-08-06 16:07   ` Suren Baghdasaryan
2021-08-08 16:13     ` Suren Baghdasaryan [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='CAJuCfpFeup+rppM7mbJWJeaCbTdbp=1=r24CjmLWWv4Vsydd2A@mail.gmail.com' \
    --to=surenb@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=christian.brauner@ubuntu.com \
    --cc=christian@brauner.io \
    --cc=david@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=guro@fb.com \
    --cc=hannes@cmpxchg.org \
    --cc=hch@infradead.org \
    --cc=jannh@google.com \
    --cc=jengelh@inai.de \
    --cc=kernel-team@android.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=luto@kernel.org \
    --cc=mhocko@suse.com \
    --cc=minchan@kernel.org \
    --cc=oleg@redhat.com \
    --cc=riel@surriel.com \
    --cc=rientjes@google.com \
    --cc=shakeelb@google.com \
    --cc=timmurray@google.com \
    --cc=willy@infradead.org \
    --subject='Re: [PATCH v7 1/2] mm: introduce process_mrelease system call' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).