| 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, 22 Sep 2007 20:37:06 +0000 (UTC) From: "Oleg Verych (nntp)" <olecom@...wer.upol.cz> To: linux-kernel@...r.kernel.org Subject: Re: memset as memzero 22-09-2007, Bernd Eckenfels: > In article <20070922124659.741cca42@...topd505.fenrus.org> you wrote: >> it doesn't add value.... memset with a constant 0 is just as fast >> (since the compiler knows it's 0) than any wrapper around it, and the >> syntax around it is otherwise the same. linux/arch/x86_64/lib/memset.S isn't file for compile, but for assembler, isn't it? Removing argument processing will have size effect. > it would however allow easier changing if you need to add a page cleaning > system (for example new architecture which has support for it). [] > On the other hand, is memset used for anything else than zero filling > or redzone "filling"? There are non zero ones (not sure what redzone is, though). > Gruss > Bernd (Here are reply-to-all people, BTW) _____ - 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