Hi! > It is entirely possible that it is just a "cycles:pp" oddity - because > the "lock xadd" is serializing, it can't retire until everything > around it has been sorted out, and maybe it just shows up in profiles > more than is really "fair" to the instruction itself, because it ends > up being that stable point for potentially hundreds of instructions > around it. Hmm, turn "lock xadd" into plain add, and see if it improves loops per second? Preferably on scratch filesystem, because you may corrupt it... Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
