linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Chengyang Fan <cy.fan@huawei.com>, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/ksm: remove unused parameter from remove_trailing_rmap_items()
Date: Tue, 30 Mar 2021 11:27:46 +0200	[thread overview]
Message-ID: <af93ede2-99c1-c5b5-e45e-641b807992a9@redhat.com> (raw)
In-Reply-To: <20210330070808.1248087-1-cy.fan@huawei.com>

On 30.03.21 09:08, Chengyang Fan wrote:
> Since commit 6514d511dbe5 ("ksm: singly-linked rmap_list") was
> merged, remove_trailing_rmap_items() doesn't use the 'mm_slot'
> parameter. So remove it, and update caller accordingly.
> 
> Signed-off-by: Chengyang Fan <cy.fan@huawei.com>
> ---
>   mm/ksm.c | 7 +++----
>   1 file changed, 3 insertions(+), 4 deletions(-)
> 
> diff --git a/mm/ksm.c b/mm/ksm.c
> index 9694ee2c71de..dd69f030c8c0 100644
> --- a/mm/ksm.c
> +++ b/mm/ksm.c
> @@ -817,8 +817,7 @@ static void remove_rmap_item_from_tree(struct rmap_item *rmap_item)
>   	cond_resched();		/* we're called from many long loops */
>   }
>   
> -static void remove_trailing_rmap_items(struct mm_slot *mm_slot,
> -				       struct rmap_item **rmap_list)
> +static void remove_trailing_rmap_items(struct rmap_item **rmap_list)
>   {
>   	while (*rmap_list) {
>   		struct rmap_item *rmap_item = *rmap_list;
> @@ -989,7 +988,7 @@ static int unmerge_and_remove_all_rmap_items(void)
>   				goto error;
>   		}
>   
> -		remove_trailing_rmap_items(mm_slot, &mm_slot->rmap_list);
> +		remove_trailing_rmap_items(&mm_slot->rmap_list);
>   		mmap_read_unlock(mm);
>   
>   		spin_lock(&ksm_mmlist_lock);
> @@ -2337,7 +2336,7 @@ static struct rmap_item *scan_get_next_rmap_item(struct page **page)
>   	 * Nuke all the rmap_items that are above this current rmap:
>   	 * because there were no VM_MERGEABLE vmas with such addresses.
>   	 */
> -	remove_trailing_rmap_items(slot, ksm_scan.rmap_list);
> +	remove_trailing_rmap_items(ksm_scan.rmap_list);
>   
>   	spin_lock(&ksm_mmlist_lock);
>   	ksm_scan.mm_slot = list_entry(slot->mm_list.next,
> 

Reviewed-by: David Hildenbrand <david@redhat.com>

-- 
Thanks,

David / dhildenb



  reply	other threads:[~2021-03-30  9:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-30  7:08 Chengyang Fan
2021-03-30  9:27 ` David Hildenbrand [this message]
2021-03-30 12:13 Chengyang Fan

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=af93ede2-99c1-c5b5-e45e-641b807992a9@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=cy.fan@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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