From: Rik van Riel <riel@conectiva.com.br>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: linux-mm@kvack.org
Subject: Re: Swap progress accounting
Date: Mon, 23 Jul 2001 15:35:28 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.33L.0107231534070.20326-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <Pine.LNX.4.33L.0107231425190.20326-100000@duckman.distro.conectiva>
On Mon, 23 Jul 2001, Rik van Riel wrote:
> On Mon, 23 Jul 2001, Arjan van de Ven wrote:
>
> > Currently, calling swap_out() on a zone doesn't count progress, and the
> > result can be that you swap_out() a lot of pages, and still return "no
> > progress possible" to try_to_free_pages(), which in turn makes a GFP_KERNEL
> > allocation fail (and that can kill init).
>
> "makes GFP_KERNEL allocation fail" ?!?!?!
OK, after talking on IRC it turns out that recursive allocations
are failing.
This isn't influenced by either changing __alloc_pages() or
by changing swap_out(). What we need to do is limit the amount
of recursive allocations going on at the same time, probably
by making the system sleep on IO completion instead of looping
like crazy in __alloc_pages()/page_launder() until we run out
of all our memory ...
regards,
Rik
--
Executive summary of a recent Microsoft press release:
"we are concerned about the GNU General Public License (GPL)"
http://www.surriel.com/
http://www.conectiva.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/
next prev parent reply other threads:[~2001-07-23 18:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-23 10:15 Arjan van de Ven
2001-07-23 17:26 ` Rik van Riel
2001-07-23 18:35 ` Rik van Riel [this message]
2001-07-23 18:41 ` Stephen C. Tweedie
2001-07-23 18:46 ` Rik van Riel
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.0107231534070.20326-100000@duckman.distro.conectiva \
--to=riel@conectiva.com.br \
--cc=arjanv@redhat.com \
--cc=linux-mm@kvack.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