On Thu, 12 May 2011, James Bottomley wrote: > On Thu, 2011-05-12 at 11:27 -0500, Christoph Lameter wrote: > > On Thu, 12 May 2011, James Bottomley wrote: > > > > > However, the fact remains that this seems to be a slub problem and it > > > needs fixing. > > > > Why are you so fixed on slub in these matters? > > Because, as has been hashed out in the thread, changing SLUB to SLAB > makes the hang go away. SLUB doesnt hang here with earlier kernel versions either. So the higher allocations are no longer as effective as they were before. This is due to a change in another subsystem. > > Its an key component but > > there is a high interaction with other subsystems. There was no recent > > change in slub that changed the order of allocations. There were changes > > affecting the reclaim logic. Slub has been working just fine with the > > existing allocation schemes for a long time. > > So suggest an alternative root cause and a test to expose it. Have a look at my other emails? I am just repeating myself again it seems. Try order = 1 which gives you SLAB like interaction with the page allocator. Then we at least know that it is the order 2 and 3 allocs that are the problem and not something else. -- 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
