linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Huang, Ying" <ying.huang@intel.com>
To: Barry Song <21cnbao@gmail.com>
Cc: Yosry Ahmed <yosryahmed@google.com>,
	 Nhat Pham <nphamcs@gmail.com>,
	Baolin Wang <baolin.wang@linux.alibaba.com>,
	 akpm@linux-foundation.org, hannes@cmpxchg.org,
	 hughd@google.com,  shakeel.butt@linux.dev, ryan.roberts@arm.com,
	 chrisl@kernel.org,  david@redhat.com, kasong@tencent.com,
	 willy@infradead.org,  viro@zeniv.linux.org.uk,
	chengming.zhou@linux.dev,  linux-mm@kvack.org,
	 kernel-team@meta.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] remove SWAP_MAP_SHMEM
Date: Wed, 25 Sep 2024 15:24:28 +0800	[thread overview]
Message-ID: <87jzf0ryab.fsf@yhuang6-desk2.ccr.corp.intel.com> (raw)
In-Reply-To: <CAGsJ_4yMxNsmPJn0W9puKWcQD3T7RDyQ=QmPhAtoq=3_u=m+TQ@mail.gmail.com> (Barry Song's message of "Wed, 25 Sep 2024 14:26:52 +0800")

Barry Song <21cnbao@gmail.com> writes:

[snip]

> I am perfectly fine with the approach, in the first loop, if we find all entries
> don't need CONTINUED, we can run the 2nd loop even for usage==1
> and nr > 1. this is almost always true for a real product where anon folios
> are unlikely to be fork-shared by so many processes.

One possible use case is ksm.  Where the map count could be large.

--
Best Regards,
Huang, Ying


  reply	other threads:[~2024-09-25  7:28 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-23 23:11 Nhat Pham
2024-09-23 23:11 ` [RFC PATCH 1/2] swapfile: add a batched variant for swap_duplicate() Nhat Pham
2024-09-23 23:11 ` [RFC PATCH 2/2] swap: shmem: remove SWAP_MAP_SHMEM Nhat Pham
2024-09-24  0:32   ` Yosry Ahmed
2024-09-24  0:20 ` [RFC PATCH 0/2] " Yosry Ahmed
2024-09-24  1:55 ` Baolin Wang
2024-09-24  2:15   ` Yosry Ahmed
2024-09-24  3:25     ` Baolin Wang
2024-09-24 14:32       ` Nhat Pham
2024-09-24 15:07         ` Yosry Ahmed
2024-09-24 15:48           ` Nhat Pham
2024-09-24 18:11             ` Yosry Ahmed
2024-09-25  6:26               ` Barry Song
2024-09-25  7:24                 ` Huang, Ying [this message]
2024-09-25  7:38                   ` Barry Song
2024-09-25  1:53             ` Baolin Wang
2024-09-25 14:37               ` Nhat Pham
2024-09-26  1:59                 ` Huang, Ying
2024-09-26  3:30                   ` Baolin Wang
2024-09-26  3:59                 ` Barry Song
2024-09-26 22:50                   ` Nhat Pham
2024-09-26  4:00                 ` Barry Song
2024-09-25  7:19             ` Huang, Ying
2024-09-25  7:32               ` Barry Song
2024-09-25 14:21                 ` Nhat Pham
2024-09-25 14:24                   ` Nhat Pham
2024-09-25 14:28                   ` Nhat Pham
2024-09-24 20:15 ` Chris Li
2024-09-24 21:30   ` Yosry Ahmed

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=87jzf0ryab.fsf@yhuang6-desk2.ccr.corp.intel.com \
    --to=ying.huang@intel.com \
    --cc=21cnbao@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=chengming.zhou@linux.dev \
    --cc=chrisl@kernel.org \
    --cc=david@redhat.com \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --cc=kasong@tencent.com \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nphamcs@gmail.com \
    --cc=ryan.roberts@arm.com \
    --cc=shakeel.butt@linux.dev \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.org \
    --cc=yosryahmed@google.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