On Thu, 12 Aug 2010, Naoya Horiguchi wrote:
quoted text > > Can you also avoid refcounts being increased during migration?
>
> Yes. I think this will be done in above-mentioned refactoring.
Thats not what I meant. Can you avoid other processors increasing
refcounts (direct I/O etc?) on any page struct of the huge page while
migration is running?
quoted text > This patch only handles migration under direct I/O.
> For the opposite (direct I/O under migration) it's not true.
> I wrote additional patches (later I'll reply to this email)
> for solving locking problem. Could you review them?
Sure.
quoted text > (Maybe these patches are beyond the scope of hugepage migration patch,
> so is it better to propose them separately?)
Migration with known races is really not what we want in the kernel.
--
unsubscribe notice To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
majordomo@vger.kernel.org
More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
http://www.tux.org/lkml/
Messages in current thread:
Re: [PATCH 0/9] Hugepage migration (v2) , Christoph Lameter , (Fri Aug 13, 5:47 am)