Re: [PATCH v2] more mapcount page as kpage could reduce total replacement times than fewer mapcount one in probability.

On Tue, 21 Jun 2016, Hugh Dickins wrote: > 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. >

Re: [PATCH v2] more mapcount page as kpage could reduce total replacement times than fewer mapcount one in probability.

On Tue, 21 Jun 2016, Hugh Dickins wrote: > 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. >

Re: [PATCH v2] more mapcount page as kpage could reduce total replacement times than fewer mapcount one in probability.

hey hugh: thank you for your reply and supplied more information. i spent lots of time to study your questions mentioned. i state my idea in detail, for exmple, page1 with map count 7 and page2 with map count 9 are equal. choosing page1 for ksm page will do 9 times heavily merg and 6

Re: [PATCH v2] more mapcount page as kpage could reduce total replacement times than fewer mapcount one in probability.

hey hugh: thank you for your reply and supplied more information. i spent lots of time to study your questions mentioned. i state my idea in detail, for exmple, page1 with map count 7 and page2 with map count 9 are equal. choosing page1 for ksm page will do 9 times heavily merg and 6

Re: [PATCH v2] more mapcount page as kpage could reduce total replacement times than fewer mapcount one in probability.

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

Re: [PATCH v2] more mapcount page as kpage could reduce total replacement times than fewer mapcount one in probability.

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

Re: [PATCH v2] more mapcount page as kpage could reduce total replacement times than fewer mapcount one in probability.

hey hugh: could you please give me some suggestion about this ? On 2016/6/15 9:56, zhouxianr...@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

Re: [PATCH v2] more mapcount page as kpage could reduce total replacement times than fewer mapcount one in probability.

hey hugh: could you please give me some suggestion about this ? On 2016/6/15 9:56, zhouxianr...@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:

[PATCH v2] more mapcount page as kpage could reduce total replacement times than fewer mapcount one in probability.

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 --- mm/ksm.c |8 1 file

[PATCH v2] more mapcount page as kpage could reduce total replacement times than fewer mapcount one in probability.

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 --- mm/ksm.c |8 1 file changed, 8 insertions(+) diff --git a/mm/ksm.c b/mm/ksm.c index