lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 16 Aug 2007 13:27:24 -0700 (PDT) From: Christoph Lameter <clameter@....com> To: Nick Piggin <npiggin@...e.de> cc: Peter Zijlstra <a.p.zijlstra@...llo.nl>, linux-mm@...ck.org, linux-kernel@...r.kernel.org, akpm@...ux-foundation.org, dkegel@...gle.com, David Miller <davem@...emloft.net>, Daniel Phillips <phillips@...gle.com> Subject: Re: [RFC 0/3] Recursive reclaim (on __PF_MEMALLOC) On Thu, 16 Aug 2007, Nick Piggin wrote: > > Honestly, I don't. They very much do not solve the problem, they just > > displace it. > > Well perhaps it doesn't work for networked swap, because dirty accounting > doesn't work the same way with anonymous memory... but for _filesystems_, > right? Regular reclaim also cannot immediately write out pages. Writes are usually deferred. If you have too many anonymous pages in regular reclaim then you can have the same issues. The difference is that recursive reclaim does not trigger writeout at the moment but we could address that by having a pageout list that then starts writes from another context. Then both reclaims would be able to trigger writeout. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists