From: Bob Breuer <breuerr@xxxxxx> Date: Wed, 09 Mar 2011 00:16:50 -0600 > My guess is that we're no longer using the special hyperSparc block copy > and fill from mm/hypersparc.S and are now leaving some data in the cache > that wasn't there before. That is a possibility. But let's be clear that this only applies to: 1) memcpy calls with constant "count" of PAGE_SIZE 2) memset calls with constant "c" of zero and "count" of PAGE_SIZE Since those are the only cases where memset/memcpy gets translated into calls to those optimized Hypersparc routines. -- 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