From: Rik van Riel <riel@conectiva.com.br>
To: safemode <safemode@speakeasy.net>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH *] 2.4.17 rmap based VM #9
Date: Sun, 30 Dec 2001 10:05:44 -0200 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.33L.0112301004560.24031-100000@imladris.surriel.com> (raw)
In-Reply-To: <1009699023.343.0.camel@psuedomode>
On 30 Dec 2001, safemode wrote:
> Seems that not all of the live-deadlocks were fixed. The one i saw in
> the last version is still present. It occurs when you're heavily
> swapping out and the nall of a sudden require something to heavily swap
I've reproduced it with 'mem=12m'. It seems the system spends all
of its time in try_to_free_pages() and friends, now I need to find
out why ;)
regards,
Rik
--
Shortwave goes a long way: irc.starchat.net #swl
http://www.surriel.com/ http://distro.conectiva.com/
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
prev parent reply other threads:[~2001-12-30 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-30 1:58 Rik van Riel
2001-12-30 7:57 ` safemode
2001-12-30 12:05 ` Rik van Riel [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=Pine.LNX.4.33L.0112301004560.24031-100000@imladris.surriel.com \
--to=riel@conectiva.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=safemode@speakeasy.net \
/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