Re:Android Project Changeset 4f8b683: libc/memset.c
by tptacek on Tuesday May 25, 2010 @09:04PM
(#1379203)
You'd unroll the loop. But knowing the average workload for memset(), it probably wouldn't be a perceptible win.
[ Parent
| on HN ]
Re:Android Project Changeset 4f8b683: libc/memset.c
by ars on Tuesday May 25, 2010 @09:55PM
(#1379281)
With todays CPU, particularly with branch prediction, and cache, loop unrolling is not always better.
In fact I bet the performance would be worse, especially because you have to worry about setting areas of memory that are not a multiple of the loop unroll size. (I guess you could use duff's device.)
I actually tested it while ignoring that, and the unrolled version took 34.551 seconds vs 34.239 for the regular version (but those number are meaningless since the variation in time between runs is greater than the difference in runtime between versions).
And see: http://lkml.indiana.edu/hypermail/linux/kernel/0008.2/0171.h... - loop unwinding is not worth it anymore.
So I ask you again pkaler: how would you speed this up?
Re:Android Project Changeset 4f8b683: libc/memset.c
by sshumaker on Tuesday May 25, 2010 @10:20PM
(#1379323)
I would imagine writing the native register size bytes per iteration would be a win, with a little cleanup for the remaining bytes. For a 32-bit architecture, you'd typically be doing 1/4 the iterations.
Re:Android Project Changeset 4f8b683: libc/memset.c
by JoeAltmaier on Wednesday May 26, 2010 @08:32AM
(#1380110)
Far more involved than that. There are alignment issues. Its several machine cycles faster to do aligned store of a large scalar e.g. 32-bit.
So a responsible implementation would do a head check for alignment, store 1,2 or 3 bytes efficiently, then do aligned stores of 32-bit values (or 64-bit or whatever native size is appropriate), then a tail check for the small change. OR better yet switch(p & 3) and handle each case with unrolled code.