From: William Lee Irwin III <wli@holomorphy.com>
To: Dan Chen <crimsun@email.unc.edu>
Cc: Rik van Riel <riel@conectiva.com.br>, linux-kernel@vger.kernel.org
Subject: Re: Memory management problems in 2.4.16
Date: Thu, 10 Jan 2002 21:01:54 -0800 [thread overview]
Message-ID: <20020110210154.A934@holomorphy.com> (raw)
In-Reply-To: <20020110224036.GA32522@atrey.karlin.mff.cuni.cz> <Pine.LNX.4.33L.0201110141090.2985-100000@imladris.surriel.com> <20020111044608.GA26644@opeth.ath.cx>
In-Reply-To: <20020111044608.GA26644@opeth.ath.cx>; from crimsun@email.unc.edu on Thu, Jan 10, 2002 at 11:46:08PM -0500
On Thu, Jan 10, 2002 at 11:46:08PM -0500, Dan Chen wrote:
> And on a PII/400 limited to "mem=64M", a `dbench 60` running with XMMS
> 1.2.6 did not cause any noticeable audio breakup. This is on 2.4.17 +
> rmap10c + ide.2.4.16.12102001 + Bill's original hashed waitqueues patch.
> (I should also add that XMMS was not running with realtime priority.)
> I'll see if I can produce some numbers in a bit.
On Fri, Jan 11, 2002 at 01:42:03AM -0200, Rik van Riel wrote:
>> I've been running a few hours of low memory testing with
>> my rmap VM and it's holding up fine. The system is still
>> responsive when the amount of pageable RAM is down to
>> about 400 kB ;))
Any chance you could include the results of the following:
/usr/sbin/readprofile -m /boot/System.map-`uname -r` | sort -rn -k1,1 | head
cat /proc/interrupts
cat /proc/slabinfo
cat /proc/meminfo
and a few lines of vmstat 10 ?
Thanks,
Bill
prev parent reply other threads:[~2002-01-11 5:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 13:34 Memory management problems in 2.4.16 Daniel Tuijnman
2002-01-09 13:39 ` Roy Sigurd Karlsbakk
2002-01-09 14:47 ` M. Edward (Ed) Borasky
2002-01-09 22:47 ` Daniel Tuijnman
2002-01-09 22:57 ` Rik van Riel
2002-01-11 0:26 ` Daniel Tuijnman
2002-01-10 22:40 ` Pavel Machek
2002-01-11 3:42 ` Rik van Riel
2002-01-11 4:46 ` Dan Chen
2002-01-11 5:01 ` William Lee Irwin III [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=20020110210154.A934@holomorphy.com \
--to=wli@holomorphy.com \
--cc=crimsun@email.unc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.