>This is going to perform really bad ... Yes, I went for space on the theory that it was not common... >and it's common for >syscalls invoked by the kernel to trigger this case. ... but so much for that theory. :-) >I'll have to think about this, thanks for pointing out the >issue. The other obvious thing is to have a bunch of userlike memcpy variants, one for each *memcpy.S file. The macros you have should make this straightforward. I was mostly worried about breaking stuff. Chris -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
