From: Mark Hemment <markhe@veritas.com>
To: linux-mm@kvack.org
Subject: PF_MEMALLOC and direct_reclaim
Date: Wed, 24 Jan 2001 19:59:09 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.21.0101241945160.26195-100000@alloc> (raw)
Hi,
Can anyone tell me the reasons a process marked PF_MEMALLOC isn't
allowed to pull pages directly off the inactive_clean lists?
I understand the reasons for PF_MEMALLOC, but not this particular
limitation. I can't find any deadlock suitation with regard to the
"pagecache_lock" and "pagemap_lru_lock" locks taken in reclaim_page(),
nor any possible case of recursion.
To successfully complete I/O (data or meta-data), kswapd (or rather, the
underlying filesystem running in the context of kswapd or any other
task marked PF_MEMALLOC) may need more memory than is directly available
via the freearea pools, while there are plenty of pages in the
inactive_clean list.
Thanks,
Mark
--
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/
reply other threads:[~2001-01-24 19:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.21.0101241945160.26195-100000@alloc \
--to=markhe@veritas.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