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: Sun, 9 Mar 2008 20:25:14 +0100 From: Ingo Molnar <mingo@...e.hu> To: Arjan van de Ven <arjan@...radead.org> Cc: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>, Thomas Gleixner <tglx@...utronix.de>, LKML <linux-kernel@...r.kernel.org>, Linus Torvalds <torvalds@...ux-foundation.org>, Andrew Morton <akpm@...ux-foundation.org>, Christoph Lameter <clameter@....com>, Bart Van Assche <bart.vanassche@...il.com> Subject: Re: quicklists confuse meminfo * Arjan van de Ven <arjan@...radead.org> wrote: > > > ouch! Could you try the patch below? How large is the quicklist > > > cache with this applied? > > > > hm, Thomas pointed it out that this wont solve all the problems as > > quicklists have a built-in "preserve me" throttle (which is rather > > stupid). > > > > the right solution is to get rid of quicklists altogether (Thomas > > expects to have patches for that later today). > > careful with this; the quicklists aren't JUST for speed they are also > there to make sure a page we free that is a pagetable, is not reused > until we have finished flushing the tlbs on all the cpus that saw it. > This is a really hard correctness requirement, and while I can see > that quicklists are probably not the best way to achieve this, we > can't just throw away the behavior ;( no, that's not true anymore - and the current quicklists code doesnt do anything like that AFAICS. It used to be a lot more complex, but now it's just a thin wrapper around the page allocator. Ingo -- 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