linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Con Kolivas <kernel@kolivas.org>
Cc: ck list <ck@vds.kolivas.org>,
	linux list <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.16-ck3
Date: Sun, 02 Apr 2006 14:46:25 +1000	[thread overview]
Message-ID: <442F5721.2040906@yahoo.com.au> (raw)
In-Reply-To: <200604021401.13331.kernel@kolivas.org>

Con Kolivas wrote:
> These are patches designed to improve system responsiveness and interactivity. 
> It is configurable to any workload but the default ck patch is aimed at the 
> desktop and cks is available with more emphasis on serverspace.
> 
> THESE INCLUDE THE PATCHES FROM 2.6.16.1 SO START WITH 2.6.16 AS YOUR BASE
> 
> Apply to 2.6.16
> http://www.kernel.org/pub/linux/kernel/people/ck/patches/2.6/2.6.16/2.6.16-ck3/patch-2.6.16-ck3.bz2
> 

The swap prefetching here, and the one in -mm AFAIKS still do not follow
the lowmem reserve ratio correctly. This might explain why prefetching
appears to help some people after updatedb swaps stuff out to make room
for pagecache -- it may actually be dipping into lower zones when it
shouldn't.

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

  reply	other threads:[~2006-04-02  8:40 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-02  4:01 2.6.16-ck3 Con Kolivas
2006-04-02  4:46 ` Nick Piggin [this message]
2006-04-02  8:51   ` 2.6.16-ck3 Con Kolivas
2006-04-02  9:37     ` 2.6.16-ck3 Nick Piggin
2006-04-02  9:39     ` [ck] 2.6.16-ck3 Con Kolivas
2006-04-02  9:51       ` Nick Piggin
2006-04-03  2:48         ` lowmem_reserve question Con Kolivas
2006-04-03  4:42           ` Mike Galbraith
2006-04-03  4:48             ` Con Kolivas
2006-04-03  4:50               ` [ck] " Con Kolivas
2006-04-03  5:14               ` Mike Galbraith
2006-04-03  5:18                 ` Con Kolivas
2006-04-03  5:31                   ` Mike Galbraith
2006-04-04  2:35           ` [ck] " Con Kolivas
2006-04-06  1:10             ` [PATCH] mm: limit lowmem_reserve Con Kolivas
2006-04-06  1:29               ` Respin: " Con Kolivas
2006-04-06  2:43                 ` Andrew Morton
2006-04-06  2:55                   ` Con Kolivas
2006-04-06  2:58                     ` Con Kolivas
2006-04-06  3:40                       ` Andrew Morton
2006-04-06  4:36                         ` Con Kolivas
2006-04-06  4:52                           ` Con Kolivas
2006-04-07  6:25               ` Nick Piggin
2006-04-07  9:02                 ` Con Kolivas
2006-04-07 12:40                   ` Nick Piggin
2006-04-08  0:15                     ` Con Kolivas
2006-04-08  0:55                       ` Nick Piggin
2006-04-08  1:01                         ` Con Kolivas
2006-04-08  1:25                           ` Nick Piggin
2006-05-17 14:11                             ` Con Kolivas
2006-05-18  7:11                               ` Nick Piggin
2006-05-18  7:21                                 ` Con Kolivas
2006-05-18  7:26                                   ` Nick Piggin

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=442F5721.2040906@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=ck@vds.kolivas.org \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).