From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Marc Singer <elf@buici.com>
Cc: William Lee Irwin III <wli@holomorphy.com>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: vmscan.c heuristic adjustment for smaller systems
Date: Sun, 18 Apr 2004 15:19:59 +1000 [thread overview]
Message-ID: <40820FFF.8090906@yahoo.com.au> (raw)
In-Reply-To: <20040418051024.GA19595@flea>
Marc Singer wrote:
> On Sun, Apr 18, 2004 at 02:41:12PM +1000, Nick Piggin wrote:
>
>>William Lee Irwin III wrote:
>>
>>>On Sun, Apr 18, 2004 at 01:37:45PM +1000, Nick Piggin wrote:
>>>
>>>
>>>>swappiness is pretty arbitrary and unfortunately it means
>>>>different things to machines with different sized memory.
>>>>Also, once you *have* gone past the reclaim_mapped threshold,
>>>>mapped pages aren't really given any preference above
>>>>unmapped pages.
>>>>I have a small patchset which splits the active list roughly
>>>>into mapped and unmapped pages. It might hopefully solve your
>>>>problem. Would you give it a try? It is pretty stable here.
>>>
>>>
>>>It would be interesting to see the results of this on Marc's system.
>>>It's a more comprehensive solution than tweaking numbers.
>>>
>>
>>Well, here is the current patch against 2.6.5-mm6. -mm is
>>different enough from -linus now that it is not 100% trivial
>>to patch (mainly the rmap and hugepages work).
>
>
> Will this work against 2.6.5 without -mm6?
>
Unfortunately it won't patch easily. If this is a big
problem for you I could make you up a 2.6.5 version.
> As an aside, I've been using SVN to manage my kernel sources. While
> I'd be thrilled to make it work, it simply doesn't seem to have the
> heavy lifting capability to handle the kernel work. I know the
> rudiments of using BK. What I'd like is some sort of HOWTO with
> example of common tasks for kernel development. Know of any?
>
Well I don't do a great deal of coding or merging, but I
use Andrew Morton's patch scripts which make things very
easy for me.
Regarding bitkeeper, I have never tried it but there is
some help in Documentation/BK-usage/ which might be of
use to you.
next prev parent reply other threads:[~2004-04-18 5:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-17 19:38 vmscan.c heuristic adjustment for smaller systems William Lee Irwin III
2004-04-17 21:29 ` Marc Singer
2004-04-17 21:33 ` William Lee Irwin III
2004-04-17 21:52 ` Marc Singer
2004-04-18 1:06 ` William Lee Irwin III
2004-04-18 5:05 ` Marc Singer
2004-04-17 23:21 ` Andrew Morton
2004-04-17 23:30 ` Marc Singer
2004-04-17 23:51 ` Andrew Morton
2004-04-18 0:11 ` Trond Myklebust
2004-04-18 0:23 ` Marc Singer
2004-04-18 3:37 ` Nick Piggin
2004-04-18 4:17 ` William Lee Irwin III
2004-04-18 4:41 ` Nick Piggin
2004-04-18 5:10 ` Marc Singer
2004-04-18 5:19 ` Nick Piggin [this message]
2004-04-18 5:35 ` Marc Singer
2004-04-18 5:41 ` Nick Piggin
2004-04-18 23:44 ` Marc Singer
2004-04-18 9:29 ` Russell King
2004-04-18 1:59 ` William Lee Irwin III
2004-04-18 3:53 ` Andrew Morton
2004-04-18 5:38 ` Marc Singer
2004-04-18 5:52 ` Andrew Morton
2004-04-18 6:15 ` Marc Singer
2004-04-19 0:26 ` Rik van Riel
2004-04-19 0:39 ` Marc Singer
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=40820FFF.8090906@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=elf@buici.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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