| 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, 15 Nov 2007 18:50:51 -0800 (PST) From: David Miller <davem@...emloft.net> To: clameter@....com Cc: corbet@....net, andi@...stfloor.org, akpm@...ux-foundation.org, linux-kernel@...r.kernel.org, dada1@...mosbay.com, schwidefsky@...ibm.com Subject: Re: [patch 01/28] cpu alloc: The allocator From: Christoph Lameter <clameter@....com> Date: Thu, 15 Nov 2007 18:19:37 -0800 (PST) > On Thu, 15 Nov 2007, David Miller wrote: > > > Well, the first version of the patch set, the one I tested, did > > require a lot of BSS space. And that's the one they are writing > > about. > > I am running the same version that you also ran. The problem is that you > did not configure the stuff properly for your box and I did not include a > configuration for sparc64 since I did not know how it needed to be > configured for sparc64. You ignored the patch for sparc64 that I provided > to correct the problem. If you're talking about the VMEMMAP thing, that patch didn't remove the problem, it simply added optimizations for sparc64 so that you could sweep the problem under the rug. Sparc32 is still broken, as just one of several possible examples. The BSS usage is still there for platforms that don't use VMEMMAP. So again, the lwn.net report is accurate. - 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