> Yes but running with this patch would allow us to verify that we understand > what is causing the problem. There are other solutions like skipping to the > next partial slab on the list that could fix performance issues that the patch > may cause. A test will give us: > > 1. Confirmation that the memory use is caused by the trylock. > > 2. Some performance numbers. If these show a regression then we have some > markers that we can measure other solutions against. okey. I will confirm its patch at next week. (unfortunately, my company don't business in rest this week) Thanks. -- 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
