* PF_MEMALLOC and direct_reclaim
@ 2001-01-24 19:59 Mark Hemment
0 siblings, 0 replies; only message in thread
From: Mark Hemment @ 2001-01-24 19:59 UTC (permalink / raw)
To: linux-mm
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/
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2001-01-24 19:54 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-01-24 19:59 PF_MEMALLOC and direct_reclaim Mark Hemment
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox