]> git.openfabrics.org - ~shefty/libmlx4.git/commit
Don't use memcpy() to write blueflame sends
authorJack Morgenstein <jackm@mellanox.co.il>
Thu, 24 Jan 2008 23:53:26 +0000 (15:53 -0800)
committerRoland Dreier <rolandd@cisco.com>
Thu, 24 Jan 2008 23:53:26 +0000 (15:53 -0800)
commitf2533e88c1c7daf4d5618612520eb58b0cff6373
tree7ba37265c810183ba07a6108336298cb99f2ef84
parent16ec68c225c41ea0e090b6200385e11e783c2ef7
Don't use memcpy() to write blueflame sends

Some memcpy() implementations may use move-string-buffer assembly
instructions, which do not guarantee copy order into the blueflame
buffer.  This causes problems when writing into a blueflame buffer, so
use our own copy function instead.

Signed-off-by: Jack Morgenstein <jackm@mellanox.co.il>
Signed-off-by: Roland Dreier <rolandd@cisco.com>
src/qp.c