Re: x86-64: memset()/memcpy() not fully standards compliant

[hpanvin@xxxxxxxxx]

Yes, I think it is probably Just A Bug.  Unless it can be shown it makes it much slower, let's fix.

Jan Beulich <JBeulich@xxxxxxxx> wrote:

>Forever these two functions have been limited to deal with at most 4G
>at a time. While I cannot point out an in-tree user that would require
>larger sizes, it is now the second time that within our Xen kernel we
>got
>bitten by that limitation. Would you nevertheless accept a patch to
>eliminate those shortcomings (iirc there may need to be workarounds
>for CPU bugs when it comes to using string instructions on such large
>blocks, albeit memmove() doesn't seem to care)?
>
>Otherwise, is there any rationale for this sort of lurking bug?
>
>Thanks, Jan

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/