From: Andrea Arcangeli <andrea@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux MM <linux-mm@kvack.org>,
Linux Kernel <linux-kernel@vger.rutgers.edu>
Subject: Re: 2.2.1{3,4,5pre*} VM bug found
Date: Tue, 25 Jan 2000 19:15:43 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.10.10001251906370.14600-100000@d251.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.10.10001250421090.482-100000@mirkwood.dummy.home>
On Tue, 25 Jan 2000, Rik van Riel wrote:
>calls __get_free_pages(). When we're (almost) out of
>memory, the process will wake up kswapd and try to
You'll block also before to go out of memory if the allocation rate is
high enough.
>In 2.2.15pre4 or when the call to try_to_free_pages()
>generates disk I/O, the task will call schedule().
>Since the task state != TASK_RUNNABLE, schedule() will
>immedately remove it from the run queue ...
Before calling schedule() you always gets registered in a waitqueue so
you can't deadlock or wait too much.
If something there is the opposite problem. If you do:
__set_current_state(TASK_UNINTERRUPTIBLE);
get_page(GFP_KERNEL);
XXXXXXXXXXXXXXXXXXXX
schedule();
then at point XXXXXXX you may become a task running and you don't block
anymore.
Andrea
--
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.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-01-25 18:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-25 3:27 2.2.1{3,4,5pre*} VM bug found Rik van Riel
2000-01-25 18:15 ` Andrea Arcangeli [this message]
2000-01-26 0:48 ` Rik van Riel
2000-01-27 19:09 ` Stephen C. Tweedie
2000-01-27 19:07 ` Stephen C. Tweedie
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.10.10001251906370.14600-100000@d251.suse.de \
--to=andrea@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.rutgers.edu \
--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 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.