From: Minchan Kim <minchan.kim@gmail.com>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
kamezawa.hiroyu@jp.fujitsu.com, kosaki.motohiro@jp.fujitsu.com
Subject: Re: [PATCH 2/2] use oom_killer_disabled in page fault oom path
Date: Tue, 26 Apr 2011 17:21:48 +0900 [thread overview]
Message-ID: <BANLkTingHBoK4mtsHkhZxW=p1GcxCjzRsQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimzYwa87NJ0F4AEN=9EZs=3-5SBaA@mail.gmail.com>
On Tue, Apr 26, 2011 at 5:07 PM, Minchan Kim <minchan.kim@gmail.com> wrote:
> On Tue, Apr 26, 2011 at 2:31 PM, Dave Young <hidave.darkstar@gmail.com> wrote:
>> Currently oom_killer_disabled is only used in __alloc_pages_slowpath,
>> For page fault oom case it is not considered. One use case is
>> virtio balloon driver, when memory pressure is high, virtio ballooning
>> will cause oom killing due to such as page fault oom.
>
> Other mm guys already accepted but sorry I can't understand your point
> since I am not familiar with virtio.
>
> Now oom_killer_disabled is used by only hibernation and hibernation
> freezes processes so page fault shouldn't happen.
>
> Now are you using oom_killer_disabled in virtio?
> Could you elaborate use case ?
Sorry, I lost your [1/2] in my mail box.
I will see it in marc linux-mm
--
Kind regards,
Minchan Kim
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2011-04-26 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 5:31 [PATCH 2/2] use oom_killer_disabled in page fault oom path Dave Young
2011-04-26 5:19 ` KAMEZAWA Hiroyuki
2011-04-26 5:51 ` KOSAKI Motohiro
2011-04-26 8:07 ` Minchan Kim
2011-04-26 8:21 ` Minchan Kim [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='BANLkTingHBoK4mtsHkhZxW=p1GcxCjzRsQ@mail.gmail.com' \
--to=minchan.kim@gmail.com \
--cc=hidave.darkstar@gmail.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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;
as well as URLs for NNTP newsgroup(s).