From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f199.google.com (mail-pf0-f199.google.com [209.85.192.199]) by kanga.kvack.org (Postfix) with ESMTP id D1B526B0005 for ; Tue, 21 Jun 2016 21:39:38 -0400 (EDT) Received: by mail-pf0-f199.google.com with SMTP id g62so75931772pfb.3 for ; Tue, 21 Jun 2016 18:39:38 -0700 (PDT) Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com. [2607:f8b0:400e:c03::22a]) by mx.google.com with ESMTPS id h82si43474872pfd.43.2016.06.21.18.39.38 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Jun 2016 18:39:38 -0700 (PDT) Received: by mail-pa0-x22a.google.com with SMTP id bz2so11495598pad.1 for ; Tue, 21 Jun 2016 18:39:38 -0700 (PDT) Date: Tue, 21 Jun 2016 18:39:29 -0700 (PDT) From: Hugh Dickins Subject: Re: [PATCH v2] more mapcount page as kpage could reduce total replacement times than fewer mapcount one in probability. In-Reply-To: <2460b794-92f0-d115-c729-bcfe33663e48@huawei.com> Message-ID: References: <1465955818-101898-1-git-send-email-zhouxianrong@huawei.com> <2460b794-92f0-d115-c729-bcfe33663e48@huawei.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org List-ID: To: zhouxianrong Cc: linux-mm@kvack.org, akpm@linux-foundation.org, hughd@google.com, aarcange@redhat.com, kirill.shutemov@linux.intel.com, dave.hansen@linux.intel.com, zhouchengming1@huawei.com, geliangtang@163.com, linux-kernel@vger.kernel.org, zhouxiyu@huawei.com, wanghaijun5@huawei.com On Tue, 21 Jun 2016, zhouxianrong wrote: > hey hugh: > could you please give me some suggestion about this ? I must ask you to be more patient: everyone would like me to be quicker, but I cannot; and this does not appear to be urgent. Your idea makes sense to me; but if your patch seems obvious to you, sorry, it isn't obvious to me. The two pages are not symmetrical, the caller of try_to_merge_two_pages() thinks it knows which is which, swapping them around underneath it like this is not obviously correct. Your patch may be fine, but I've not had time to think it through: will do, but not immediately. Your idea may not make so much sense to Andrea: he has been troubled by the difficulty in unmapping a KSM page with a very high mapcount. And you would be maximizing a buggy case, if we think of that page being mapped also into non-VM_MERGEABLE areas; but I think we can ignore that aspect, it's buggy already, and I don't think anyone really cares deeply about madvise(,,MADV_UNMERGEABLE) correctness on forked areas. KSM was not originally written with fork in mind. I have never seen such a long title for a patch: maybe "[PATCH] ksm: choose the more mapped for the KSM page". > > On 2016/6/15 9:56, zhouxianrong@huawei.com wrote: > > From: z00281421 > > > > more mapcount page as kpage could reduce total replacement times > > than fewer mapcount one when ksmd scan and replace among > > forked pages later. > > > > Signed-off-by: z00281421 And I doubt that z00281421 is your real name: see Documentation/SubmittingPatches. Hugh > > --- > > mm/ksm.c | 8 ++++++++ > > 1 file changed, 8 insertions(+) > > > > diff --git a/mm/ksm.c b/mm/ksm.c > > index 4786b41..4d530af 100644 > > --- a/mm/ksm.c > > +++ b/mm/ksm.c > > @@ -1094,6 +1094,14 @@ static struct page *try_to_merge_two_pages(struct > > rmap_item *rmap_item, > > { > > int err; > > > > + /* > > + * select more mapcount page as kpage > > + */ > > + if (page_mapcount(page) < page_mapcount(tree_page)) { > > + swap(page, tree_page); > > + swap(rmap_item, tree_rmap_item); > > + } > > + > > err = try_to_merge_with_ksm_page(rmap_item, page, NULL); > > if (!err) { > > err = try_to_merge_with_ksm_page(tree_rmap_item, > > -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org