public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peter@programming.kicks-ass.net>
To: Wu Fengguang <wfg@mail.ustc.edu.cn>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
	riel@redhat.com, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 01/16] mm: delayed page activation
Date: Thu, 10 Nov 2005 10:17:44 +0100	[thread overview]
Message-ID: <1131614264.14052.25.camel@localhost.localdomain> (raw)
In-Reply-To: <20051109141432.393114000@localhost.localdomain>

On Wed, 2005-11-09 at 21:49 +0800, Wu Fengguang wrote:
> plain text document attachment (mm-delayed-activation.patch)
> When a page is referenced the second time in inactive_list, mark it with
> PG_activate instead of moving it into active_list immediately. The actual
> moving work is delayed to vmscan time.
> 
> This implies two essential changes:
> - keeps the adjecency of pages in lru;
> - lifts the page reference counter max from 1 to 3.
> 
> And leads to the following improvements:
> - read-ahead for a leading reader will not be disturbed by a following reader;
> - enables the thrashing protection logic to save pages for following readers;
> - keeping relavant pages together helps improve I/O efficiency;
> - and also helps decrease vm fragmantation;
> - increased refcnt space might help page replacement algorithms.

I'm working on a clockpro implementation that essentialy keeps all
resident pages on 1 clock. In this case readahead pages will also not
fragment over the active/inactive lists but stay in order. Would that
also satisfy your requirements?

Code can be found at:
  http://programming.kicks-ass.net/kernel-patches/clockpro-2/

Note however that this is work in progress and rather unstable, there
are some livelock scenarios in there.

Kind regards,

Peter Zijlstra



  parent reply	other threads:[~2005-11-10  9:17 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-09 13:49 [PATCH 00/16] Adaptive read-ahead V7 Wu Fengguang
2005-11-09 13:49 ` [PATCH 01/16] mm: delayed page activation Wu Fengguang
2005-11-10  0:21   ` Nick Piggin
2005-11-10  3:15     ` Wu Fengguang
2005-11-10  9:17   ` Peter Zijlstra [this message]
2005-11-10 10:30     ` Wu Fengguang
2005-11-09 13:49 ` [PATCH 02/16] mm: balance page aging between zones Wu Fengguang
2005-11-09 13:49 ` [PATCH 03/16] radixtree: sync with mainline Wu Fengguang
2005-11-09 13:49 ` [PATCH 04/16] radix-tree: look-aside cache Wu Fengguang
2005-11-09 23:31   ` Nick Piggin
2005-11-10  5:25     ` Wu Fengguang
2005-11-10  6:50       ` Nick Piggin
2005-11-10  8:30         ` Wu Fengguang
2005-11-18 11:25         ` Wu Fengguang
2005-11-18 12:12           ` Wu Fengguang
2005-11-09 13:49 ` [PATCH 05/16] readahead: some preparation Wu Fengguang
2005-11-18  7:46   ` 2.6.15-rc1-mm2 Andrew Morton
2005-11-18  8:56     ` 2.6.15-rc1-mm2 Benoit Boissinot
2005-11-18  9:04       ` 2.6.15-rc1-mm2 Andrew Morton
2005-11-18  9:13         ` 2.6.15-rc1-mm2 Benoit Boissinot
2005-11-18 13:43         ` 2.6.15-rc1-mm2 Rafael J. Wysocki
2005-11-18 10:10     ` 2.6.15-rc1-mm2 Mauro Carvalho Chehab
2005-11-18 10:55     ` 2.6.15-rc1-mm2 Wu Fengguang
2005-11-18 11:29     ` 2.6.15-rc1-mm2 Andy Whitcroft
2005-11-18 16:29     ` 2.6.15-rc1-mm2 Michael Krufky
2005-11-20  0:23     ` 2.6.15-rc1-mm2 Michal Piotrowski
2005-11-20  8:04       ` 2.6.15-rc1-mm2 Hugh Dickins
2005-11-20 12:53         ` 2.6.15-rc1-mm2 Michal Piotrowski
2005-11-09 13:49 ` [PATCH 06/16] readahead: call scheme Wu Fengguang
2005-11-09 13:49 ` [PATCH 07/16] readahead: tunable parameters Wu Fengguang
2005-11-09 13:49 ` [PATCH 08/16] readahead: state based method Wu Fengguang
2005-11-09 13:49 ` [PATCH 09/16] readahead: context " Wu Fengguang
2005-11-09 13:49 ` [PATCH 10/16] readahead: other methods Wu Fengguang
2005-11-09 13:49 ` [PATCH 11/16] readahead: mandatory thrashing protection Wu Fengguang
2005-11-09 13:49 ` [PATCH 12/16] readahead: events accounting Wu Fengguang
2005-11-09 13:49 ` [PATCH 13/16] readahead: page aging accounting Wu Fengguang
2005-11-09 13:49 ` [PATCH 14/16] readahead: laptop mode support Wu Fengguang
2005-11-09 13:49 ` [PATCH 15/16] readahead: disable look-ahead for loopback file Wu Fengguang
2005-11-09 13:49 ` [PATCH 16/16] io: reduce lantency Wu Fengguang
2005-11-09 20:39 ` [PATCH 00/16] Adaptive read-ahead V7 Christoph Lameter
2005-11-10 10:19   ` Wu Fengguang
  -- strict thread matches above, loose matches on Subject: below --
2005-12-03  7:14 [PATCH 00/16] Adaptive read-ahead V9 Wu Fengguang
2005-12-03  7:14 ` [PATCH 01/16] mm: delayed page activation Wu Fengguang
2005-12-04 12:11   ` Nikita Danilov
2005-12-04 13:48     ` Wu Fengguang
2005-12-04 15:03       ` Nikita Danilov
2005-12-04 19:10         ` Peter Zijlstra
2005-12-05  1:48         ` Wu Fengguang
2005-12-06 17:55           ` Nikita Danilov
2005-12-07  1:42             ` Wu Fengguang
2005-12-07  9:46               ` Andrew Morton
2005-12-07 10:36                 ` Wu Fengguang
2005-12-07 12:44               ` Nikita Danilov
2005-12-07 13:53                 ` Wu Fengguang

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=1131614264.14052.25.camel@localhost.localdomain \
    --to=peter@programming.kicks-ass.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=riel@redhat.com \
    --cc=wfg@mail.ustc.edu.cn \
    /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