Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 23, 2013
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
Glibc change exposing bugs
Posted Nov 10, 2010 21:03 UTC (Wed) by fuhchee (subscriber, #40059)
Posted Nov 10, 2010 23:05 UTC (Wed) by patrick_g (subscriber, #44470)
Posted Nov 11, 2010 0:26 UTC (Thu) by jwb (guest, #15467)
Posted Nov 11, 2010 5:01 UTC (Thu) by nicooo (guest, #69134)
Posted Nov 11, 2010 6:54 UTC (Thu) by madscientist (subscriber, #16861)
So it doesn't sound useless to me.
Posted Nov 11, 2010 9:42 UTC (Thu) by dgm (subscriber, #49227)
Posted Nov 11, 2010 12:00 UTC (Thu) by alankila (subscriber, #47141)
It would probably be better idea for majority of systems to just remove memcpy() and just replace it with memmove() which showed up with 0.17 %. Together, that would add up to 0.5 % at most, I suppose.
Posted Nov 11, 2010 16:26 UTC (Thu) by jedbrown (subscriber, #49919)
Posted Nov 11, 2010 0:57 UTC (Thu) by MattPerry (guest, #46341)
But we don't know if he ran his test on that computer. There's not enough information to tie the two together. It would help if Linus stated what CPU he used to run the test on.
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds