From: Andrea Arcangeli <andrea@suse.de>
To: Abraham vd Merwe <abraham@2d3d.co.za>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.16 & OOM killer screw up
Date: Tue, 11 Dec 2001 01:02:23 +0100 [thread overview]
Message-ID: <20011211010223.Z4801@athlon.random> (raw)
In-Reply-To: <20011210101452.F1502@crystal.2d3d.co.za>
In-Reply-To: <20011210101452.F1502@crystal.2d3d.co.za>; from abraham@2d3d.co.za on Mon, Dec 10, 2001 at 10:14:52AM +0200
On Mon, Dec 10, 2001 at 10:14:52AM +0200, Abraham vd Merwe wrote:
> Hi!
>
> If I leave my machine on for a day or two without doing anything on it (e.g.
> my machine at work over a weekend) and I come back then 1) all my memory is
> used for buffers/caches and when I try running application, the OOM killer
> kicks in, tries to allocate swap space (which I don't have) and kills
> whatever I try start (that's with 300M+ memory in buffers/caches).
I'd try 2.4.17pre4aa1.
Andrea
prev parent reply other threads:[~2001-12-11 0:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-10 8:14 2.4.16 & OOM killer screw up Abraham vd Merwe
2001-12-10 18:46 ` Marcelo Tosatti
2001-12-11 0:02 ` Andrea Arcangeli [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=20011211010223.Z4801@athlon.random \
--to=andrea@suse.de \
--cc=abraham@2d3d.co.za \
--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