From: "Bryan Wu" <cooloney@kernel.org>
To: "Hennerich, Michael" <Michael.Hennerich@analog.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
dwmw2@infradead.org
Subject: Re: [PATCH 1/4] [mm] buddy page allocator: add tunable big order allocation
Date: Wed, 14 May 2008 12:22:35 +0800 [thread overview]
Message-ID: <386072610805132122l5d017fe1u404c38ea3f05664a@mail.gmail.com> (raw)
In-Reply-To: <8A42379416420646B9BFAC9682273B6D015F52E4@limkexm3.ad.analog.com>
On Tue, May 13, 2008 at 7:42 PM, Hennerich, Michael
<Michael.Hennerich@analog.com> wrote:
>
>
> >-----Original Message-----
> >From: KAMEZAWA Hiroyuki [mailto:kamezawa.hiroyu@jp.fujitsu.com]
> >Sent: Dienstag, 13. Mai 2008 04:09
> >To: Bryan Wu
> >Cc: linux-kernel@vger.kernel.org; linux-mm@kvack.org;
> dwmw2@infradead.org;
> >Michael Hennerich
> >Subject: Re: [PATCH 1/4] [mm] buddy page allocator: add tunable big
> order
> >allocation
> >
> >On Mon, 12 May 2008 18:32:02 +0800
> >Bryan Wu <cooloney@kernel.org> wrote:
> >
> >> From: Michael Hennerich <michael.hennerich@analog.com>
> >>
> >> Signed-off-by: Michael Hennerich <michael.hennerich@analog.com>
> >> Signed-off-by: Bryan Wu <cooloney@kernel.org>
> >
> >Does this really solve your problem ? possible hang-up is better than
> >page allocation failure ?
>
> On nommu this helped quite a bit, when we run out of memory, eaten up by
> the page cache. But yes - with this option it's likely that we sit there
> and wait form memory that might never get available.
>
> We now use a better workaround for freeing up "available" memory
> currently used as page cache.
>
> I think we should drop this patch.
>
OK, I dropped it. And do you think the limited page_cache patch is the
replacement of this patch?
-Bryan
--
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:[~2008-05-14 4:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 10:32 [PATCH 0/4] Memory management patches from Blackfin team Bryan Wu
2008-05-12 10:32 ` [PATCH 1/4] [mm] buddy page allocator: add tunable big order allocation Bryan Wu, Michael Hennerich
2008-05-13 2:09 ` KAMEZAWA Hiroyuki
2008-05-13 11:42 ` Hennerich, Michael
2008-05-14 4:22 ` Bryan Wu [this message]
2008-05-14 5:04 ` KAMEZAWA Hiroyuki
2008-05-12 10:32 ` [PATCH 2/4] [NOMMU]: include the problematic mapping in the munmap warning Bryan Wu, Mike Frysinger
2008-05-15 6:33 ` Bryan Wu
2008-05-12 10:32 ` [PATCH 3/4] [mm/nommu]: use copy_to_user_page to call flush icache for [#811] toolchain old bug Bryan Wu, Jie Zhang
2008-05-15 6:24 ` Bryan Wu
2008-05-12 10:32 ` [PATCH 4/4] [MM/NOMMU]: Export two symbols in nommu.c for mmap test Bryan Wu, Vivi Li
2008-05-12 10:38 ` Mike Frysinger
2008-05-12 13:00 ` Christoph Hellwig
2008-05-12 13:02 ` Mike Frysinger
2008-05-13 7:09 ` Bryan Wu
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=386072610805132122l5d017fe1u404c38ea3f05664a@mail.gmail.com \
--to=cooloney@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=dwmw2@infradead.org \
--cc=kamezawa.hiroyu@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).