LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Aubrey Li" <aubreylee@gmail.com>
To: "Vaidyanathan Srinivasan" <svaidy@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
"Linus Torvalds" <torvalds@osdl.org>,
"Andrew Morton" <akpm@osdl.org>,
"Nick Piggin" <nickpiggin@yahoo.com.au>,
"linux-os (Dick Johnson)" <linux-os@analogic.com>,
"Robin Getz" <rgetz@blackfin.uclinux.org>
Subject: Re: [RPC][PATCH 2.6.20-rc5] limit total vfs page cache
Date: Fri, 19 Jan 2007 23:40:20 +0800 [thread overview]
Message-ID: <6d6a94c50701190740v6da25151kb9ddcf358ab2957@mail.gmail.com> (raw)
In-Reply-To: <45B0D967.8090607@linux.vnet.ibm.com>
On 1/19/07, Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com> wrote:
>
> Hi Aubrey,
>
> I used your patch on my PPC64 box and I do not get expected
> behavior. As you had requested, I am attaching zoneinfo and meminfo
> dumps:
>
> Please let me know if you need any further data to help me out with
> the test/experiment.
>
Although I have no PPC64 box in hand, I think the logic should be the same.
get_page_from_freelist() is called 5 times in __alloc_pages().
1) alloc_flags = ALLOC_WMARK_LOW | ALLOC_PAGECACHE;
2) alloc_flags = ALLOC_WMARK_MIN | ALLOC_PAGECACHE;
We should have the same result on the first two times get_page_from_freelist().
3) if (((p->flags & PF_MEMALLOC) || unlikely(test_thread_flag(TIF_MEMDIE)))
&& !in_interrupt())
alloc_flags = ALLOC_NO_WATERMARKS
The case on my platform will never enter this branch. If the branch
occurs on your side,
The limit will be omitted. Because NO watermark, zone_watermark_ok()
will not be checked. memory will be allocated directly.
4)if (likely(did_some_progress)) {
alloc_flags should include ALLOC_PAGECACHE.
So we should have the same result on this call.
5) } else if ((gfp_mask & __GFP_FS) && !(gfp_mask & __GFP_NORETRY)) {
alloc_flags = ALLOC_WMARK_HIGH, without ALLOC_PAGECACHE
This branch will not hit on my case. You may need to check it.
If 3) or 5) occurs on your platform, I think you can easily fix it.
Please confirm it and let me know the result.
Thanks,
-Aubrey
next prev parent reply other threads:[~2007-01-19 15:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 3:23 Aubrey Li
2007-01-19 14:44 ` Vaidyanathan Srinivasan
2007-01-19 15:40 ` Aubrey Li [this message]
2007-01-24 5:30 ` Vaidyanathan Srinivasan
2007-01-24 5:53 ` Aubrey Li
2007-01-19 14:52 ` Vaidyanathan Srinivasan
2007-01-19 16:05 ` Aubrey Li
2007-01-19 18:49 ` Vaidyanathan Srinivasan
2007-01-19 19:01 ` Christoph Lameter
2007-01-20 2:04 ` Aubrey Li
2007-01-20 2:24 ` Nick Piggin
2007-01-20 2:35 ` Mike Frysinger
2007-01-20 2:49 ` Nick Piggin
2007-01-20 3:40 ` Mike Frysinger
2007-01-20 3:08 ` Aubrey Li
2007-01-20 4:03 ` Nick Piggin
2007-01-20 4:26 ` Aubrey Li
2007-01-22 19:22 ` Christoph Lameter
2007-01-22 19:15 ` Christoph Lameter
2007-01-19 18:21 ` Christoph Lameter
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=6d6a94c50701190740v6da25151kb9ddcf358ab2957@mail.gmail.com \
--to=aubreylee@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-os@analogic.com \
--cc=nickpiggin@yahoo.com.au \
--cc=rgetz@blackfin.uclinux.org \
--cc=svaidy@linux.vnet.ibm.com \
--cc=torvalds@osdl.org \
--subject='Re: [RPC][PATCH 2.6.20-rc5] limit total vfs page cache' \
/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
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).