Re: [PATCH 7/8] mm,oom: Stop clearing TIF_MEMDIE on remote thread.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed 13-07-16 00:45:59, Tetsuo Handa wrote:
> Michal Hocko wrote:
> > On Tue 12-07-16 22:29:22, Tetsuo Handa wrote:
> > > Since no kernel code path needs to clear TIF_MEMDIE flag on a remote
> > > thread we can drop the task parameter and enforce that actually.
> > > 
> > > Signed-off-by: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
> > > Acked-by: Michal Hocko <mhocko@xxxxxxxx>
> > 
> > Please wait with this one along with removing exit_oom_victim from the
> > oom reaper after we settle with the rest of the series. I believe we
> > really need to handle oom_killer_disable in the same batch and that
> > sounds outside of the scope of this series.
> > 
> > I can even pick your patch and rebase it along with the rest that I have
> > posted recently, unless you have objections of course.
> 
> I have no objections. Please insert my patches into your series.

Let's wait after the merge window closes and things calm down. In the
mean time it would be great to summarize pros and cons of the two
approach so that we can decide properly and have this for future
reference.

Thanks!
-- 
Michal Hocko
SUSE Labs

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



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]