From: Minchan Kim <minchan.kim@gmail.com>
To: 우충기 <chungki.woo@gmail.com>, "Mel Gorman" <mel@csn.ul.ie>
Cc: Minchan Kim <minchan.kim@gmail.com>,
ngupta@vflare.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, fengguang.wu@intel.com, riel@redhat.com,
akpm@linux-foundation.org, kosaki.motohiro@jp.fujitsu.com
Subject: Re: abnormal OOM killer message
Date: Wed, 19 Aug 2009 15:49:58 +0900 [thread overview]
Message-ID: <20090819154958.18a34aa5.minchan.kim@barrios-desktop> (raw)
In-Reply-To: <18eba5a10908182324x45261d06y83e0f042e9ee6b20@mail.gmail.com>
On Wed, 19 Aug 2009 15:24:54 +0900
i??i?(C)e,? <chungki.woo@gmail.com> wrote:
> Thank you very much for replys.
>
> But I think it seems not to relate with stale data problem in compcache.
> My question was why last chance to allocate memory was failed.
> When OOM killer is executed, memory state is not a condition to
> execute OOM killer.
> Specially, there are so many pages of order 0. And allocating order is zero.
> I think that last allocating memory should have succeeded.
> That's my worry.
Yes. I agree with you.
Mel. Could you give some comment in this situation ?
Is it possible that order 0 allocation is failed
even there are many pages in buddy ?
>
> -----------------------------------------------------------------------------------------------------------------------------------------------
> page = get_page_from_freelist(gfp_mask|__GFP_HARDWALL, order,
> <== this is last chance
> zonelist, ALLOC_WMARK_HIGH|ALLOC_CPUSET);
> <== uses ALLOC_WMARK_HIGH
> if (page)
> goto got_pg;
>
> out_of_memory(zonelist, gfp_mask, order);
> goto restart;
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
> > Let me have a question.
> > Now the system has 79M as total swap.
> > It's bigger than system memory size.
> > Is it possible in compcache?
> > Can we believe the number?
>
> Yeah, It's possible. 79Mbyte is data size can be swap.
> It's not compressed data size. It's just original data size.
You means your pages with 79M are swap out in compcache's reserved
memory?
>
> Thanks,
> Minchan, Nitin
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-08-19 6:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 1:41 우충기
2009-08-19 2:44 ` Minchan Kim
2009-08-19 3:44 ` Nitin Gupta
2009-08-19 4:51 ` Minchan Kim
2009-08-19 6:24 ` 우충기
2009-08-19 6:49 ` Minchan Kim [this message]
2009-08-19 7:14 ` Chungki woo
2009-08-19 7:29 ` Minchan Kim
2009-08-19 8:25 ` Nitin Gupta
2009-08-19 8:42 ` Minchan Kim
2009-08-19 10:36 ` Mel Gorman
2009-08-19 10:52 ` Minchan Kim
2009-08-19 10:58 ` Mel Gorman
2009-08-19 11:01 ` Minchan Kim
2009-08-19 12:06 ` Chungki woo
2009-08-19 10:18 ` Minchan Kim
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=20090819154958.18a34aa5.minchan.kim@barrios-desktop \
--to=minchan.kim@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chungki.woo@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=ngupta@vflare.org \
--cc=riel@redhat.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