On Wed, Apr 16 2008, Andi Kleen wrote: > > > There have been various implementations of queue_work_on() posted > > through the years, I've had one version that I've used off and on for a > > long time: > > queue_work_on is the wrong interface I think. You rather > want a pool of non pinned threads that are then load balanced by the > scheduler (who knows best what cpus have cycles available) Yeah, that actually sounds like the best interface. What I described typically ends up trying to be too clever, you really want to leave any scheduling decisions to the scheduler. -- Jens Axboe -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
