On Wed, Dec 21, 2011 at 7:12 AM, Oleg Nesterov <email@example.com> wrote:
>> + * * /*
>> + * * ** FIXME: this should be io_schedule(). *The timeout is there as a
>> + * * ** workaround for some DM problems in 2.6.18.
>> + * * **/
>> + * * io_schedule_timeout(5*HZ);
> Just curious... This was added by 0b1d647a in 2006.
> Perhaps the problem was already fixed?
Yeah, I was curious about that too. It seemed the problem was dm
sharing the same pool from multiple devices (which defeats the purpose
of using mempool BTW). cc'ing dm devel. Alasdair, is the problem
dm-devel mailing list