Just one more thing. On Tue, Apr 05, 2016 at 10:01:07AM -0400, Tejun Heo wrote: ... > > pool_info in spin lock context, made me allocate memory to get all > > values upfront through allocation. > > Now that the lock is going away, I can do what you have described above. So, this might be okay depending on the use case but it often becomes painful to require sleeping context for freeing resources. If you're certain that requiring sleeping context is okay for all paths, using a single mutex is fine but *usually* it isn't a great idea. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
