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: Sat, 7 Apr 2007 17:21:38 -0700 (PDT) From: Christoph Lameter <clameter@....com> To: Andrew Morton <akpm@...ux-foundation.org> cc: Hugh Dickins <hugh@...itas.com>, Nick Piggin <npiggin@...e.de>, dgc@....com, linux-kernel@...r.kernel.org Subject: Re: [PATCH 2/2] Optimize compound_head() by avoiding a shared page flag On Sat, 7 Apr 2007, Andrew Morton wrote: > Which is all a ton of fun, but this subversion of the architecture's > freedom to use volatile, memory barriers etc is a worry. We do the same in > page_alloc.c, of course... I just tried the approach that we discussed earlier and it was not nice either. Lets just use a page flag please. This check will be in several hot code paths. And it may become more important because the file system folks want to support buffers > page size. Then we may want more transparent support for huge pages... For all of this page->private gets in the way. And I think we curently have 5 or so page flags available? - 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