From: "John Fremlin" <vii@penguinpowered.com>
To: Roger Larsson <roger.larsson@norran.net>
Cc: linux-mm@kvack.org
Subject: [PATCH] Re: latancy test of -ac22-riel
Date: 22 Jun 2000 20:11:29 +0100 [thread overview]
Message-ID: <m2ya3xsf8e.fsf@boreas.southchinaseas> (raw)
In-Reply-To: <394FB013.3B21EA28@norran.net>
Roger Larsson <roger.larsson@norran.net> writes:
[...]
> I retried running with normal prio - then I get stalls
> of > 350ms...
I think some stalls are most probably due to try_to_free_pages below
page_alloc.c::__alloc_pages
/*
* Uhhuh. All the zones have been critical, which means that
* we'd better do some synchronous swap-out. kswapd has not
* been able to cope..
*/
if (!(current->flags & PF_MEMALLOC)) {
if (!try_to_free_pages(gfp_mask)) {
if (!(gfp_mask & __GFP_HIGH))
goto fail;
}
goto fail;
}
That is, it happens in times of high memory stress and when I comment
it out the pauses go away but I'm not sure that this is a good
long-term solution ;-) though IMHO the behaviour without it (VM
killing process) is better than the behaviour with it (paging until
power is cycled).
[...]
--
http://altern.org/vii
--
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-06-22 19:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-19 23:57 [itcompilesshipitPATCH] -ac22-riel vm improvement? Rik van Riel
2000-06-20 0:11 ` Juan J. Quintela
2000-06-20 6:13 ` latancy test of -ac22-riel Roger Larsson
[not found] ` <m2u2eoxwzx.fsf@boreas.southchinaseas>
[not found] ` <394FB013.3B21EA28@norran.net>
2000-06-22 19:11 ` John Fremlin [this message]
2000-06-22 19:47 ` [PATCH] " Rik van Riel
2000-06-23 1:09 ` John Fremlin
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=m2ya3xsf8e.fsf@boreas.southchinaseas \
--to=vii@penguinpowered.com \
--cc=linux-mm@kvack.org \
--cc=roger.larsson@norran.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