From: "Stephen C. Tweedie" <sct@redhat.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Arjan van de Ven <arjanv@redhat.com>, linux-mm@kvack.org
Subject: Re: Swap progress accounting
Date: Mon, 23 Jul 2001 19:41:53 +0100 [thread overview]
Message-ID: <20010723194153.J31712@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33L.0107231534070.20326-100000@duckman.distro.conectiva>; from riel@conectiva.com.br on Mon, Jul 23, 2001 at 03:35:28PM -0300
Hi,
On Mon, Jul 23, 2001 at 03:35:28PM -0300, Rik van Riel wrote:
> 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 ...
That's very much the sort of thing that the reservation proposal from
a few weeks back was designed to address --- serialising access to the
last few free pages to allow the VM to proceed OK.
One gotcha is that there may be specific processes, such as loopd or
nbd servers, that need to be allowed to proceed because otherwise you
risk blocking IO requests in other independent tasks.
--Stephen
--
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:41 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
2001-07-23 18:41 ` Stephen C. Tweedie [this message]
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=20010723194153.J31712@redhat.com \
--to=sct@redhat.com \
--cc=arjanv@redhat.com \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox