| |||||||||||||
Speeding up the page allocatorSpeeding up the page allocatorPosted Feb 26, 2009 20:46 UTC (Thu) by bcopeland (subscriber, #51750)In reply to: Speeding up the page allocator by bluefoxicy Parent article: Speeding up the page allocator
> The assumption here is that the CPU's internal microcode for
> running a loop is a lot faster than stepping through two instructions:
I admit I haven't kept up with the ISAs since pentium era, but for a while the rep functions were in fact slower than open-coded loops. Anyway if it were true that rep movs was faster than dec/jmp, there is rep stosd which does the same thing but without copying.
(Log in to post comments)
Speeding up the page allocator Posted Feb 27, 2009 0:00 UTC (Fri) by bluefoxicy (guest, #25366) [Link]
stosd ... now you're talking. That's obviously a better solution: store a binary string of IMMEDIATE data, not copy memory data!
|
|||||||||||||