|
Prev: 2.6.25.2 - Jiffies/Time jumping back and forth (Regereesion from 2.6.24)
Next: [BUG] 2.6.26-rc1-git4 - task blocked on powerpc for more than 120 seconds
From: KOSAKI Motohiro on 7 May 2008 09:30 Hi nice improvement. but... > 2.6.25-rc3-mm1 2.6.25-rc3-mm1+ 2.6.25-mm1 Patched 2.6.25-mm1 > 1 1168441 1064021 876000 947488 > 2 1094264 921059 1549592 1730685 > 3 2082520 1738165 1694370 2324880 > 4 2079929 1695521 404553 2400408 > 5 2898758 406566 391283 3246580 > 6 2921417 261275 263249 3752148 > 7 3308761 126056 191742 4243142 > 8 3329456 100129 141722 4275780 > > 1st column: stock 2.6.25-rc3-mm1 > 2nd column: 2.6.25-rc3-mm1 + ipc patches (store ipcs into idrs) > 3nd column: stock 2.6.25-mm1 > 4th column: 2.6.25-mm1 + this pacth series. this result is slightly odd. similar to 2.6.25-rc3-mm1 and patched-2.6.25-mm1 similar to 2.6.25-mm1 and 2.6.25-rc3-mm1 but not similar to 2.6.25-rc3-mm1 and patched-2.6.25-rc3-mm1 not similar to 2.6.25-mm1 and patched-2.6.25-mm1 Is patched-2.6.25-rc3-mm1 and patched-2.6.25-mm1 applied the same patch? or I misunderstand how to see your chart? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |