| 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
| ||
|
Message-ID: <20090312123230.GA14425@parisc-linux.org> Date: Thu, 12 Mar 2009 06:32:30 -0600 From: Matthew Wilcox <matthew@....cx> To: Daniel Phillips <phillips@...nq.net> Cc: Nick Piggin <nickpiggin@...oo.com.au>, linux-fsdevel@...r.kernel.org, tux3@...3.org, Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org Subject: Re: [Tux3] Tux3 report: Tux3 Git tree available On Thu, Mar 12, 2009 at 05:24:33AM -0700, Daniel Phillips wrote: > On Thursday 12 March 2009, Nick Piggin wrote: > > That's interesting. Do you handle 1K block sizes with 64K page size? :) > > Not in its current incarnation. That would require 32 bytes worth of > state while the current code just has a 4 byte map (4 bits X 8 blocks). > I suppose a reasonable way to extend it would be 4 x 8 byte maps. Has > somebody spotted a 64K page? I believe SGI ship their ia64 kernels configured this way. Certainly 16k ia64 kernels are common, which would (if I understand your scheme correctly) be 8 bytes worth of state in your scheme. -- Matthew Wilcox Intel Open Source Technology Centre "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." -- 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