On Wed, 2011-12-21 at 17:31 -0800, Shi, Alex wrote: > This patch partly fixed a performance regression that triggered by > 4dcfe1025b513c2c, but issue still exists. So how much was the regression caused by the commit 4dcfe1025b513c2c and how much did we recover with this fix I posted. If we are talking about the regression caused by this single commit 4dcfe1025b513c2c, then I don't know of any other related fixes other than the recent fix we pushed upstream (ab2789213d224202237292d78aaa0c386c7b28b2). thanks, suresh -- To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|