From: Michal Hocko <mhocko@kernel.org>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
linux-mm@kvack.org, kvm@vger.kernel.org,
"Kirill A. Shutemov" <kirill@shutemov.name>
Subject: Re: KVM hang after OOM
Date: Tue, 20 Mar 2018 07:53:55 +0100 [thread overview]
Message-ID: <20180320065339.GA23100@dhcp22.suse.cz> (raw)
In-Reply-To: <CABXGCsN8mN7bGNDx9Tb2sewuXWp6DbcyKpMFv0UzGATAMELxqA@mail.gmail.com>
On Mon 19-03-18 21:23:12, Mikhail Gavrilov wrote:
> Good news 4.16.0-rc6 with proposed patch not hangs after OOM anymore!
> Of course I would be more happy If was possible protect GUI from
> memory pressing and save responsiveness from lags when system begin
It seems it is "Web Content" that is eating a lot of memory. Maybe it
would help to put this process into a dedicated memory cgroup with some
reasonable limit and thus reduce the pressure to the system as whole.
[...]
> using swap actively.
> But I'm already satisfied with proposed patch.
>
> I am attached dmesg when I triggering OOM three times. And every time
> after it system survived.
> I think this patch should be merged in mainline.
Could you be more specific what is _this_ patch, please?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-03-20 6:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-11 18:11 Mikhail Gavrilov
2018-03-12 9:00 ` Kirill A. Shutemov
2018-03-12 18:56 ` Mikhail Gavrilov
2018-03-13 12:22 ` Tetsuo Handa
2018-03-15 12:34 ` Michal Hocko
2018-03-15 12:37 ` Michal Hocko
2018-03-12 10:22 ` Tetsuo Handa
2018-03-15 11:56 ` Tetsuo Handa
2018-03-15 20:10 ` Mikhail Gavrilov
2018-03-17 3:13 ` Tetsuo Handa
2018-03-19 16:23 ` Mikhail Gavrilov
2018-03-20 6:53 ` Michal Hocko [this message]
2018-03-20 12:20 ` Tetsuo Handa
[not found] ` <CABXGCsNBEpVoMzrhyNLKhzNxPs=9a+Z+2aUxJ8WtZ8gE+=OGSA@mail.gmail.com>
2018-03-22 8:39 ` Michal Hocko
-- strict thread matches above, loose matches on Subject: below --
2018-03-11 16:50 Mikhail Gavrilov
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=20180320065339.GA23100@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=kirill@shutemov.name \
--cc=kvm@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/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