From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>,
<linuxppc-dev@lists.linuxppc.org>
Subject: Re: overnight 2.4.11 seems to have used up all memory, slow as a dog
Date: Mon, 8 Oct 2001 16:07:21 +0200 [thread overview]
Message-ID: <20011008140721.19291@smtp.adsl.oleane.com> (raw)
In-Reply-To: <20011008112806.PUYY27768.tomts5-srv.bellnexxia.net@there>
>
>Is this a symptom of the "VM" troubles that have kept me away from the
>2.4.X series?
>
>How can I track this one down?
>
>FWIW, this never happens with 2.2.19 at all (I can do long overnight
>builds with no trouble with no slowdowns.
There was at least one VM bug fixed between pre4 and pre5, you
can rsync again (or pull from bk if you are using bk _devel)
to check if it's better.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-10-08 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-08 11:30 overnight 2.4.11 seems to have used up all memory, slow as a dog Kevin B. Hendricks
2001-10-08 14:07 ` Benjamin Herrenschmidt [this message]
2001-10-09 18:04 ` Dan Malek
2001-10-09 18:56 ` Kevin Hendricks
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=20011008140721.19291@smtp.adsl.oleane.com \
--to=benh@kernel.crashing.org \
--cc=khendricks@ivey.uwo.ca \
--cc=linuxppc-dev@lists.linuxppc.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).