From: "J.A. Magallon" <jamagallon@able.es>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: ccroswhite@get2chip.com, linux-kernel@vger.kernel.org
Subject: Re: Problems with VM
Date: Fri, 15 Feb 2002 01:48:55 +0100 [thread overview]
Message-ID: <20020215014855.A14226@werewolf.able.es> (raw)
In-Reply-To: <3C6C53C0.E7562704@get2chip.com> <E16bWX6-0001hc-00@the-village.bc.nu>
In-Reply-To: <E16bWX6-0001hc-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on vie, feb 15, 2002 at 01:47:24 +0100
On 20020215 Alan Cox wrote:
>> as 'normal' ran. Consequently, I will have a machine that has 5M
>> 'normal' RAM, 800M 'cache' RAM and the reset coming out of swap space.
>> I need this 'cache' RAM placed back into the available RAM pool to be
>> used by applications. Is there a patch/kernel configuration that I can
>> change this behavior?
>
>2.4.18-rc1 should fix the worst of that. The rmap patches in 2.4.18-ac
>definitely fix it
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
Or oyu can try the next patch from Andrea Arcangeli for the vm, still
to include in mainline. I have adapted it to apply cleanly on plain
2.4.18-rc1:
http://giga.cps.unizar.es/~magallon/linux/2.4.18-rc1-slb1/00-vm-24.gz
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Mandrake Linux release 8.2 (Cooker) for i586
Linux werewolf 2.4.18-rc1-slb1 #1 SMP Thu Feb 14 01:04:12 CET 2002 i686
prev parent reply other threads:[~2002-02-15 0:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-15 0:18 ccroswhite
2002-02-15 0:22 ` Rik van Riel
2002-02-15 0:34 ` David Lang
2002-02-15 0:47 ` Alan Cox
2002-02-15 0:48 ` J.A. Magallon [this message]
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=20020215014855.A14226@werewolf.able.es \
--to=jamagallon@able.es \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ccroswhite@get2chip.com \
--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
all inboxes | Powered by JetHome®