linux-kernel - Re: quicklists confuse meminfo

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 9 Mar 2008 11:46:40 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Christoph Lameter <clameter@....com>,
	Bart Van Assche <bart.vanassche@...il.com>
Subject: Re: quicklists confuse meminfo

On Sun, 9 Mar 2008 13:34:32 +0100 Ingo Molnar <mingo@...e.hu> wrote:

> the right solution is to get rid of quicklists altogether

Yes, I think so.

- They are pretty marginal from a performance POV (iirc)

- They've been a relatively rich source of bugs

- As I said when we merged them (under protest): Private object caches
  like this are just a bad idea - caches should be *shared*, because some
  other code path which wants a zeroed page wants a cache-warm one, not a
  cache-cold one from the allocator (iirc there was doubt over how
  cache-warm these pages are, however).

  Making __GFP_ZERO smarter/more efficient would be a preferable way of
  addressing any performance problems we have in there.
--
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/