linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.cz>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org, oleg@redhat.com,
	rientjes@google.com, vdavydov@parallels.com, mst@redhat.com
Subject: Re: [PATCH 4/6] mm,oom_reaper: Make OOM reaper use list of mm_struct.
Date: Tue, 12 Jul 2016 15:46:57 +0200	[thread overview]
Message-ID: <20160712134657.GJ14586@dhcp22.suse.cz> (raw)
In-Reply-To: <201607122238.HJI78681.QOHVSMFtFJOOFL@I-love.SAKURA.ne.jp>

On Tue 12-07-16 22:38:42, Tetsuo Handa wrote:
> Michal Hocko wrote:
> > >  #define MAX_OOM_REAP_RETRIES 10
> > > -static void oom_reap_task(struct task_struct *tsk)
> > > +static void oom_reap_task(struct task_struct *tsk, struct mm_struct *mm)
> > >  {
> > >  	int attempts = 0;
> > > -	struct mm_struct *mm = NULL;
> > > -	struct task_struct *p = find_lock_task_mm(tsk);
> > >  
> > >  	/*
> > > -	 * Make sure we find the associated mm_struct even when the particular
> > > -	 * thread has already terminated and cleared its mm.
> > > -	 * We might have race with exit path so consider our work done if there
> > > -	 * is no mm.
> > > +	 * Check MMF_OOM_REAPED in case oom_kill_process() found this mm
> > > +	 * pinned.
> > >  	 */
> > > -	if (!p)
> > > -		goto done;
> > > -	mm = p->mm;
> > > -	atomic_inc(&mm->mm_count);
> > > -	task_unlock(p);
> > > +	if (test_bit(MMF_OOM_REAPED, &mm->flags))
> > > +		return;
> > >  
> > >  	/* Retry the down_read_trylock(mmap_sem) a few times */
> > >  	while (attempts++ < MAX_OOM_REAP_RETRIES && !__oom_reap_task(tsk, mm))
> > >  		schedule_timeout_idle(HZ/10);
> > >  
> > >  	if (attempts <= MAX_OOM_REAP_RETRIES)
> > > -		goto done;
> > > +		return;
> > >  
> > >  	/* Ignore this mm because somebody can't call up_write(mmap_sem). */
> > >  	set_bit(MMF_OOM_REAPED, &mm->flags);
> > 
> > This seems unnecessary when oom_reaper always calls exit_oom_mm. The
> > same applies to __oom_reap_task. Which then means that the flag is
> > turning into a misnomer. MMF_SKIP_OOM would fit better its current
> > meaning.
> 
> Large oom_score_adj value or being a child process of highest OOM score
> might cause the same mm being selected again. I think these set_bit() are
> necessary in order to avoid the same mm being selected again.

I do not understand. Child will have a different mm struct from the
parent and I do not see how oom_score_adj is relevant here. Could you
elaborate, please?

-- 
Michal Hocko
SUSE Labs

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2016-07-12 13:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-07 15:58 [PATCH v2 0/6] Change OOM killer to " Tetsuo Handa
2016-07-07 16:00 ` [PATCH 1/6] mm,oom_reaper: Reduce find_lock_task_mm() usage Tetsuo Handa
2016-07-11 12:02   ` Michal Hocko
2016-07-07 16:01 ` [PATCH 2/6] mm,oom_reaper: Do not attempt to reap a task twice Tetsuo Handa
2016-07-11 12:15   ` Michal Hocko
2016-07-07 16:03 ` [PATCH 3/6] mm,oom: Use list of mm_struct used by OOM victims Tetsuo Handa
2016-07-11 12:50   ` Michal Hocko
2016-07-12  6:00     ` Tetsuo Handa
2016-07-12  7:09       ` Michal Hocko
2016-07-07 16:04 ` [PATCH 4/6] mm,oom_reaper: Make OOM reaper use list of mm_struct Tetsuo Handa
2016-07-11 13:16   ` Michal Hocko
2016-07-12 13:38     ` Tetsuo Handa
2016-07-12 13:46       ` Michal Hocko [this message]
2016-07-12 13:55         ` Michal Hocko
2016-07-12 14:01           ` Tetsuo Handa
2016-07-07 16:06 ` [PATCH 5/6] mm,oom: Remove OOM_SCAN_ABORT case and signal_struct->oom_victims Tetsuo Handa
2016-07-11 13:19   ` Michal Hocko
2016-07-07 16:07 ` [PATCH 6/6] mm,oom: Stop clearing TIF_MEMDIE on remote thread Tetsuo Handa
2016-07-11 13:22   ` Michal Hocko

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=20160712134657.GJ14586@dhcp22.suse.cz \
    --to=mhocko@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=mst@redhat.com \
    --cc=oleg@redhat.com \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=rientjes@google.com \
    --cc=vdavydov@parallels.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