Nick, what's the plan for going ahead with the VFS scalability work? We're pretty late in the 2.6.36 cycle now and it would be good to get the next batch prepared and reivew so that it can get some testing in -next. As mentioned before my preference would be the inode lock splitup and related patches - they are relatively simple and we're already seeing workloads where inode_lock really hurts in the writeback code. -- 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
