public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Shantanu Goel <sgoel01@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: [VM PATCH 2.6.6-rc3-bk5] Dirty balancing in the presence of mapped pages
Date: Wed, 05 May 2004 12:16:41 +1000	[thread overview]
Message-ID: <40984E89.6070501@yahoo.com.au> (raw)
In-Reply-To: <20040504180345.099926ec.akpm@osdl.org>

Andrew Morton wrote:
> Shantanu Goel <sgoel01@yahoo.com> wrote:
> 
>>Presently the kernel does not collection information
>>about the percentage of memory that processes have
>>dirtied via mmap until reclamation.  Nothing analogous
>>to balance_dirty_pages() is being done for mmap'ed
>>pages.  The attached patch adds collection of dirty
>>page information during kswapd() scans and initiation
>>of background writeback by waking up bdflush.
> 
> 
> And what were the effects of this patch?
> 

I havea modified patch from Nikita that does the
if (ptep_test_and_clear_dirty) set_page_dirty from
page_referenced, under the page_table_lock.

So it also picks up pages coming off the active list.

It doesn't do the wakeup_bdflush thing, but that sounds
like a good idea. What does wakeup_bdflush(-1) mean?


  reply	other threads:[~2004-05-05  2:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-05  0:20 [VM PATCH 2.6.6-rc3-bk5] Dirty balancing in the presence of mapped pages Shantanu Goel
2004-05-05  1:03 ` Andrew Morton
2004-05-05  2:16   ` Nick Piggin [this message]
2004-05-05  2:57     ` Andrew Morton
2004-05-05  3:16       ` Nick Piggin
2004-05-05  3:24         ` Nick Piggin
2004-05-09 17:24         ` Bill Davidsen
2004-05-05  4:31       ` Shantanu Goel
2004-05-05  5:25         ` Andrew Morton
2004-05-05 16:56       ` Nikita Danilov

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=40984E89.6070501@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sgoel01@yahoo.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