From: Minchan Kim <minchan@kernel.org>
To: paul.szabo@sydney.edu.au
Cc: linux-mm@kvack.org, 695182@bugs.debian.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Subtract min_free_kbytes from dirtyable memory
Date: Wed, 23 Jan 2013 10:49:59 +0900 [thread overview]
Message-ID: <20130123014959.GB2723@blaptop> (raw)
In-Reply-To: <201301210315.r0L3FnGV021298@como.maths.usyd.edu.au>
On Mon, Jan 21, 2013 at 02:15:49PM +1100, paul.szabo@sydney.edu.au wrote:
> When calculating amount of dirtyable memory, min_free_kbytes should be
> subtracted because it is not intended for dirty pages.
So what's the effect for user?
It would be better to include that in description if possible.
>
> Using an "extern int" because that is the only interface to some such
> sysctl values.
>
> (This patch does not solve the PAE OOM issue.)
>
> Paul Szabo psz@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/
> School of Mathematics and Statistics University of Sydney Australia
>
> Reported-by: Paul Szabo <psz@maths.usyd.edu.au>
> Reference: http://bugs.debian.org/695182
> Signed-off-by: Paul Szabo <psz@maths.usyd.edu.au>
>
> --- mm/page-writeback.c.old 2012-12-06 22:20:40.000000000 +1100
> +++ mm/page-writeback.c 2013-01-21 13:57:05.000000000 +1100
> @@ -343,12 +343,16 @@
> unsigned long determine_dirtyable_memory(void)
> {
> unsigned long x;
> + extern int min_free_kbytes;
>
> x = global_page_state(NR_FREE_PAGES) + global_reclaimable_pages();
>
> if (!vm_highmem_is_dirtyable)
> x -= highmem_dirtyable_memory(x);
>
> + /* Subtract min_free_kbytes */
> + x -= min(x, min_free_kbytes >> (PAGE_SHIFT - 10));
It seems you saw old kernel.
Current kernel includes following logic.
static unsigned long global_dirtyable_memory(void)
{
unsigned long x;
x = global_page_state(NR_FREE_PAGES) + global_reclaimable_pages();
x -= min(x, dirty_balance_reserve);
if (!vm_highmem_is_dirtyable)
x -= highmem_dirtyable_memory(x);
return x + 1; /* Ensure that we never return 0 */
}
And dirty_lanace_reserve already includes high_wmark_pages.
Look at calculate_totalreserve_pages.
So I think we don't need this patch.
Thanks.
> +
> return x + 1; /* Ensure that we never return 0 */
> }
>
> --
> 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>
--
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:[~2013-01-23 1:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 3:15 [PATCH] Subtract min_free_kbytes from dirtyable memory paul.szabo
2013-01-21 17:49 ` Rik van Riel
2013-01-22 23:38 ` Andrew Morton
2013-01-23 1:49 ` Minchan Kim [this message]
2013-01-23 3:11 ` paul.szabo
-- strict thread matches above, loose matches on Subject: below --
2013-01-25 9:53 paul.szabo
2013-01-28 6:23 ` Minchan Kim
2013-01-25 13:01 Bug#695182: " Ben Hutchings
2013-01-25 23:49 ` paul.szabo
2013-01-26 0:14 ` Jonathan Nieder
2013-01-26 15:43 ` Theodore Ts'o
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=20130123014959.GB2723@blaptop \
--to=minchan@kernel.org \
--cc=695182@bugs.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paul.szabo@sydney.edu.au \
/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).