On Thu, Jan 26, 2012 at 05:11:36PM +0100, Jan Kara wrote: > wait_log_commit() and wait_for_writer() were using slightly different > conditions for deciding whether they should call schedule() and whether they > should continue in the wait loop. Thus it could happen that we busylooped when > the first condition was not true while the second one was. That is burning CPU > cycles needlessly and is deadly on UP machines...
Thanks Jan, I'll pull this in. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
