Re: OOM killer changes

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

 



On Thu 25-08-16 13:35:04, Ralf-Peter Rohbeck wrote:
[...]
> Sorry, the tag was next-20160823; I called the branch linux-next-20160823.

Yeah that is the tag I was looking for but the linux-next is quite
volatile and if you do not fetch the particular tag it won't exist in
leter trees. Anyway, I have set up a branch oom-playground in my tree
git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git which which
is on top of the current up-to-date mmotm tree + revert of the quick
workaround which you have already tested (thanks for that!) and with
the Vlastimil's patch which was dropped due to workaround. AFAIU this
is what you have previously tested without OOM but later on still
managed to hit OOM again. Which would suggest we are still not there
and need to investigate further. I have some ideas what to do but I
would appreciate if we can confirm this status before we try new things.

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]