I know that memcpy, memset, and the related functions in Windows are optimized to copy 16 bytes at a time.
Is ReactOS optimized this way, or is it slow as hell (copying/setting 1 byte at a time in the data loop)?
So many things are dependent on copying data as fast as possible.
GvG wrote:Depends on whether you introduce bugs I guess I'd be interested if you see a measurable performance improvement.
This will be one of the first things I will test, as soon as I can compile ReactOS. I still haven't downloded GCC and all the stuff needed. I'm very interested in working with ReactOS in the future
blight wrote:I doubt that this will improve overall speed - you would have to save and restore the MMX/SSE state before and after using such opcodes (KeSaveFloatingPointState/KeRestoreFloatingPointState - check MSDN: Using Floating Point or MMX in a WDM Driver for more information)
Okay, so these calls may slow down things. Well, it was worth asking at least.