On Fri, 8 Jun 2007, Andreas Kleen wrote: > > That's what kmem_cache_alloc() is for?!?! > > Tradtionally that was not allowed in block layer path. Not sure > it is fully obsolete with the recent dirty tracking work, probably not.
Why was it not allowed? Because interrupts are disabled? > Besides it would need to be GFP_ATOMIC and the default > atomic pools are not that big. Those could be increased. I think Mel has them already increased in mm. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
