Re: [RFC 7/7] Switch of PF_MEMALLOC during writeout

Christoph Lameter <[email protected]> writes:

> Switch off PF_MEMALLOC during both direct and kswapd reclaim.
> 
> This works because we are not holding any locks at that point because
> reclaim is essentially complete. The write occurs when the memory on
> the zones is at the high water mark so it is unlikely that writeout
> will get into trouble. If so then reclaim can be called recursively to
> reclaim more pages.

What would stop multiple recursions in extreme low memory cases? Seems 
risky to me and risking stack overflow.  Perhaps define another flag to catch that?

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [RFC 7/7] Switch of PF_MEMALLOC during writeout
    • From: Christoph Lameter <[email protected]>

• References:
  • [RFC 0/7] Postphone reclaim laundry to write at high water marks
    • From: Christoph Lameter <[email protected]>
  • [RFC 7/7] Switch of PF_MEMALLOC during writeout
    • From: Christoph Lameter <[email protected]>

• Prev by Date: Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
• Next by Date: Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
• Previous by thread: [RFC 7/7] Switch of PF_MEMALLOC during writeout
• Next by thread: Re: [RFC 7/7] Switch of PF_MEMALLOC during writeout
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]