| 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: <8bd0f97a0703292053l2391d6eeh7440d7633301fdae@mail.gmail.com> Date: Thu, 29 Mar 2007 23:53:59 -0400 From: "Mike Frysinger" <vapier.adi@...il.com> To: bryan.wu@...log.com Cc: "Andrew Morton" <akpm@...ux-foundation.org>, "David Howells" <dhowells@...hat.com>, linux-kernel@...r.kernel.org Subject: Re: [PATCH] nommu arch dont zero the anonymous mapping by adding UNINITIALIZE flag On 3/29/07, Wu, Bryan <bryan.wu@...log.com> wrote: > On architectures with MMU, malloc takes about the same speed, > indepentant of malloc size, while on the Blackfin (NOMMU), as the malloc > size increases, the time that malloc consumes grows.... err, this is not the direction we wanted to go ... this requires changes to the user<->kernel boundary which certainly will be rejected by the glibc maintainers since it implies breakage in POSIX behavior and is specific to no-mmu only ... the plan is to hold onto this cruft in Blackfin until we get this bug sorted out: http://blackfin.uclinux.org/gf/project/uclinux-dist/tracker/?action=TrackerItemEdit&tracker_item_id=3027 as the thing we'll send to mainline will be sane (a no-mmu specific kconfig option to control the memset in the kernel malloc) the memset in the kernel right now for no-mmu is by design, not defect ... we can chat about this more via Blackfin channels if you like, or just wait till we meet up in Shanghai -mike - 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