linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Jinjiang Tu <tujinjiang@huawei.com>
Cc: <david@redhat.com>, <shr@devkernel.io>, <hannes@cmpxchg.org>,
	<riel@surriel.com>, <wangkefeng.wang@huawei.com>,
	<sunnanyong@huawei.com>, <linux-mm@kvack.org>
Subject: Re: [PATCH] mm/ksm: remove redundant code in ksm_fork
Date: Wed, 3 Apr 2024 18:45:48 -0700	[thread overview]
Message-ID: <20240403184548.44798417e068b79469505ffb@linux-foundation.org> (raw)
In-Reply-To: <20240402024934.1093361-1-tujinjiang@huawei.com>

On Tue, 2 Apr 2024 10:49:34 +0800 Jinjiang Tu <tujinjiang@huawei.com> wrote:

> Since commit 3c6f33b7273a ("mm/ksm: support fork/exec for prctl"), when a
> child process is forked, the MMF_VM_MERGE_ANY flag will be inherited in
> mm_init(). So, it's unnecessary to set the flag in ksm_fork().
> 
> ...
>
> --- a/include/linux/ksm.h
> +++ b/include/linux/ksm.h
> @@ -45,16 +45,8 @@ static inline void ksm_might_unmap_zero_page(struct mm_struct *mm, pte_t pte)
>  
>  static inline int ksm_fork(struct mm_struct *mm, struct mm_struct *oldmm)
>  {
> -	int ret;
> -
> -	if (test_bit(MMF_VM_MERGEABLE, &oldmm->flags)) {
> -		ret = __ksm_enter(mm);
> -		if (ret)
> -			return ret;
> -	}
> -
> -	if (test_bit(MMF_VM_MERGE_ANY, &oldmm->flags))
> -		set_bit(MMF_VM_MERGE_ANY, &mm->flags);
> +	if (test_bit(MMF_VM_MERGEABLE, &oldmm->flags))
> +		return __ksm_enter(mm);
>  
>  	return 0;

Thanks, I shall queue this up for testing and shall await review input
from Stefan and hopefully others.



  reply	other threads:[~2024-04-04  1:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-02  2:49 Jinjiang Tu
2024-04-04  1:45 ` Andrew Morton [this message]
     [not found] ` <cddc0d26-5163-462e-bb9e-7fd87aacad37@redhat.com>
2024-04-06 23:37   ` Jinjiang Tu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240403184548.44798417e068b79469505ffb@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-mm@kvack.org \
    --cc=riel@surriel.com \
    --cc=shr@devkernel.io \
    --cc=sunnanyong@huawei.com \
    --cc=tujinjiang@huawei.com \
    --cc=wangkefeng.wang@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox