[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOS58YP6ogHaadh1Pjf_jF0+zwecJ7aZjQceisH9xTZ5GTTy4w@mail.gmail.com>
Date: Wed, 21 Dec 2011 07:34:21 -0800
From: Tejun Heo <tj@...nel.org>
To: Oleg Nesterov <oleg@...hat.com>
Cc: Pavel Mironchik <tibor0@...il.com>,
Alasdair G Kergon <agk@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kernel@...r.kernel.org, dm-devel@...hat.com
Subject: Re: mempool && io_schedule_timeout()
Hello,
On Wed, Dec 21, 2011 at 7:12 AM, Oleg Nesterov <oleg@...hat.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
fixed now?
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists