On Fri, 2010-04-23 at 22:18 +0300, Pekka J Enberg wrote: > On Thu, 22 Apr 2010, Pekka Enberg wrote: > >>> The following bug entry is on the current list of known regressions > >>> from 2.6.33. Please verify if it still should be listed and let the > >>> tracking team > >>> know (either way). > >> > >> I have not been able to reproduce it so far. > > > > So what are our options? We can revert the SLUB conversion patch for now > > but > > I still can't see what's wrong with it... I also don't know why. The original patch looks good.
> > I haven't been able to reproduce this either on my Core 2 machine. Mostly, the regression exists on Nehalem machines. I suspect it's related to hyper-threading machine. > > Yanmin, does something like this help on your machines? A quick testing doesn't show any help. I did a new testing. After the machine boots, I hot remove 8 hyper-threading cpu which means last 8 are just cores. The regression between 2.6.33 and 2.6.34-rc becomes small. My opinion is we needn't revert the patch, but still keep an eye on it when testing other new RC kernel releases. One reason is volanoMark and netperf have no such regression. Is it ok? Yanmin -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
