From: Mel Gorman <mgorman@suse.de>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: minchan.kim@gmail.com, abarry@cray.com,
akpm@linux-foundation.org, linux-mm@kvack.org, riel@redhat.com,
hannes@cmpxchg.org, linux-kernel@vger.kernel.org
Subject: Re: Unending loop in __alloc_pages_slowpath following OOM-kill; rfc: patch.
Date: Tue, 24 May 2011 10:16:11 +0100 [thread overview]
Message-ID: <20110524091611.GD5279@suse.de> (raw)
In-Reply-To: <4DDB74F7.9020109@jp.fujitsu.com>
On Tue, May 24, 2011 at 06:05:59PM +0900, KOSAKI Motohiro wrote:
> >>> Why?
> >>
> >> Otherwise, we don't have good PCP dropping trigger. Big machine might have
> >> big pcp cache.
> >>
> >
> > Big machines also have a large cost for sending IPIs.
>
> Yes. But it's only matter if IPIs are frequently happen.
> But, drain_all_pages() is NOT only IPI source. some vmscan function (e.g.
> try_to_umap) makes a lot of IPIs.
>
> Then, it's _relatively_ not costly. I have a question. Do you compare which
> operation and drain_all_pages()? IOW, your "costly" mean which scenario suspect?
>
I am concerned that if the machine gets into trouble and we are failing
to reclaim that sending more IPIs is not going to help any. There is no
evidence at the moment that sending extra IPIs here will help anything.
--
Mel Gorman
SUSE Labs
--
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>
next prev parent reply other threads:[~2011-05-24 9:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 21:31 Andrew Barry
2011-05-17 10:34 ` Minchan Kim
2011-05-17 11:34 ` Mel Gorman
2011-05-17 15:49 ` Andrew Barry
2011-05-18 22:29 ` Minchan Kim
2011-05-20 16:49 ` Minchan Kim
2011-05-20 17:16 ` Rik van Riel
2011-05-20 17:23 ` Mel Gorman
2011-05-24 4:54 ` KOSAKI Motohiro
2011-05-24 5:45 ` KOSAKI Motohiro
2011-05-24 8:30 ` Mel Gorman
2011-05-24 8:36 ` KOSAKI Motohiro
2011-05-24 8:49 ` Mel Gorman
2011-05-24 9:05 ` KOSAKI Motohiro
2011-05-24 9:16 ` Mel Gorman [this message]
2011-05-24 9:40 ` KOSAKI Motohiro
2011-05-24 10:57 ` Mel Gorman
2011-05-24 23:53 ` KOSAKI Motohiro
2011-05-24 8:34 ` Minchan Kim
2011-05-24 8:41 ` KOSAKI Motohiro
2011-05-24 8:57 ` Minchan Kim
2011-05-24 9:36 ` KOSAKI Motohiro
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=20110524091611.GD5279@suse.de \
--to=mgorman@suse.de \
--cc=abarry@cray.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--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