From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kosaki.motohiro@jp.fujitsu.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Marcelo Tosatti <marcelo@kvack.org>,
Rik van Riel <riel@redhat.com>,
Daniel Spang <daniel.spang@gmail.com>
Subject: Re: [RFC][PATCH] a bit improvement of ZONE_DMA page reclaim
Date: Fri, 18 Jan 2008 20:11:22 +0900 [thread overview]
Message-ID: <20080118200423.8FBC.KOSAKI.MOTOHIRO@jp.fujitsu.com> (raw)
In-Reply-To: <20080118162434.8FB1.KOSAKI.MOTOHIRO@jp.fujitsu.com>
Hi Andrew,
> > > on X86, ZONE_DMA is very very small.
> > > It is often no used at all.
> >
> > In that case page-reclaim is supposed to set all_unreclaimable and
> > basically ignores the zone altogether until it looks like something might
> > have changed.
> >
> > Is that code not working? (quite possible).
>
> please insert blow debug printk and dd if=bigfile of=/dev/null.
> you see "near_oom(DMA) 0 0 0" messages :)
sorry, my last mail is not enough description.
It is not so useful at solo use.
As you say, If long time passes all_unreclaimable turn on and
incorrect shrink list become no happned.
but, my mem_notify patch very dislike incorrect shrink ;-)
result as, I don't hope quick merge.
and I will merge to my mem_notify patch series.
Thanks.
- kosaki
--
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>
prev parent reply other threads:[~2008-01-18 11:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 6:34 KOSAKI Motohiro
2008-01-18 7:21 ` Andrew Morton
2008-01-18 7:28 ` KOSAKI Motohiro
2008-01-18 11:11 ` KOSAKI Motohiro [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=20080118200423.8FBC.KOSAKI.MOTOHIRO@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=daniel.spang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marcelo@kvack.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