[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4D40C687.2020202@np.css.fujitsu.com>
Date: Thu, 27 Jan 2011 10:12:39 +0900
From: Jin Dongming <jin.dongming@...css.fujitsu.com>
To: Andrea Arcangeli <aarcange@...hat.com>
CC: Andi Kleen <andi@...stfloor.org>,
AKPM <akpm@...ux-foundation.org>,
Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>,
Huang Ying <ying.huang@...el.com>,
LKLM <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/3] Avoid unmapping THP when it is failed to be split.
Hi, Andrea
(2011/01/26 7:01), Andrea Arcangeli wrote:
> On Tue, Jan 25, 2011 at 02:45:27PM +0900, Jin Dongming wrote:
>> If the THP is failed to be split,
>> 1. The processes using the poisoned page could not be collected.
>> (Because page_mapped_in_vma() in collect_procs_anon() always
>> returns NULL.)
>
> page_mapped_in_vma is only called after split_huge_page without
> requiring this change.
>
>> 2. The poisoned page could not be unmapped.
>> (If CONFIG_DEBUG_VM is "y", VM_BUG_ON(PageTransHuge(page))
>> in try_to_unmap() will be called, and system panic will be
>> caused.)
>
> This is more reasonable argument for the change because at times
> collect_procs may fail kmalloc or for other reasons kill may be set to
> 1 without split_huge_page having run.
>
>> 3. The processes using the poisoned page could not be killed, too.
>> (Because no process is collected in 1.)
>
> I don't see the point of the change for 1.
>
I am sorry for my poor description.
>> So if splitting THP is failed, it is better to stop unmapping
>> rather than causing panic. System might servive if the page is freed
>> later.
>
> Splitting THP can't fail unless the page is freed under
> split_huge_page (like if the process quits while you're calling
> split_huge_page and in turn the anon_vma was already unusable).
>
Basically I agree with you.
But this patch could do the following things.
1st, as your comment for point 2, this patch could avoid
unexpected failure which is not the real failure of
split_huge_page().
2nd, from the result of failure of split_huge_page(),
the operations after it is not meaningful any more or
unexpected.
3rd, this patch can reduce the account of patches after it.
So I will modify the description like following.
1. Describe the result of failure of split_huge_page() clearly.
2. Add the reason why move split_huge_page() here.
How do you think about it?
> Patch looks good but just for point 2.
Thanks.
Best Regards,
Jin Dongming
> --
> 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/
>
>
--
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