From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Nikita Danilov <nikita@clusterfs.com>
Subject: Re: [PATCH 3/3] vm: writeout watermarks
Date: Tue, 08 Nov 2005 10:12:01 +1100 [thread overview]
Message-ID: <436FDF41.9090106@yahoo.com.au> (raw)
In-Reply-To: <20051107153337.GB17246@logos.cnet>
Marcelo Tosatti wrote:
> Nikita has a customer using large percentage of RAM for
> a kernel module, which results in get_dirty_limits() misbehaviour
> since
>
> unsigned long available_memory = total_pages;
>
> It should work on the amount of cacheable pages instead.
>
> He's got a patch but I dont remember the URL. Nikita?
>
Indeed. This patch has a couple of little problems anyway, and
probably does not logicaly belong as part of this series.
I'll work on previous 2 more important patches first.
My patch should probably go on top of more fundamental work
like Nikita's patch.
Thanks,
Nick
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2005-11-07 23:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 5:18 [PATCH 0/3] better zone and watermark balancing Nick Piggin
2005-11-01 5:19 ` [PATCH 1/3] vm: kswapd incmin Nick Piggin
2005-11-01 5:20 ` [PATCH 2/3] vm: highmem watermarks Nick Piggin
2005-11-01 5:21 ` [PATCH 3/3] vm: writeout watermarks Nick Piggin
2005-11-07 15:33 ` Marcelo Tosatti
2005-11-07 21:13 ` Nikita Danilov
2005-11-07 23:12 ` Nick Piggin [this message]
2005-11-07 15:28 ` [PATCH 1/3] vm: kswapd incmin Marcelo Tosatti
2005-11-07 23:08 ` Nick Piggin
2005-11-07 18:43 ` Marcelo Tosatti
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=436FDF41.9090106@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=nikita@clusterfs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.