linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Baolin Wang <baolin.wang@linux.alibaba.com>
Cc: akpm@linux-foundation.org, hughd@google.com, david@redhat.com,
	wangkefeng.wang@huawei.com, kasong@tencent.com,
	ying.huang@linux.alibaba.com, 21cnbao@gmail.com,
	ryan.roberts@arm.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mm: shmem: skip swapcache for swapin of synchronous swap device
Date: Mon, 6 Jan 2025 04:07:21 +0000	[thread overview]
Message-ID: <Z3tW-bSC6ze8HtSS@casper.infradead.org> (raw)
In-Reply-To: <8344980d-4c22-4694-9a76-2e5a7ada50cb@linux.alibaba.com>

On Mon, Jan 06, 2025 at 11:46:04AM +0800, Baolin Wang wrote:
> On 2025/1/2 21:10, Matthew Wilcox wrote:
> > On Thu, Jan 02, 2025 at 04:40:17PM +0800, Baolin Wang wrote:
> > > With fast swap devices (such as zram), swapin latency is crucial to applications.
> > > For shmem swapin, similar to anonymous memory swapin, we can skip the swapcache
> > > operation to improve swapin latency.
> > 
> > OK, but now we have more complexity.  Why can't we always skip the
> > swapcache on swapin?
> 
> Skipping swapcache is used to swap-in shmem large folios, avoiding the large
> folios being split. Meanwhile, since the IO latency of syncing swap devices
> is relatively small, it won't cause the IO latency amplification issue.
> 
> But for async swap devices, if we swap-in the large folio one-time, I am
> afraid the IO latency can be amplified. And I remember we still haven't
> reached an agreement here[1], so let's step by step and start with the sync
> swap devices first.

Regardless of whether we choose to swap-in an order-0 or a large folio,
my point is that we should always do it to the pagecache rather than the
swap cache.



  reply	other threads:[~2025-01-06  4:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-02  8:40 Baolin Wang
2025-01-02 13:10 ` Matthew Wilcox
2025-01-06  3:46   ` Baolin Wang
2025-01-06  4:07     ` Matthew Wilcox [this message]
2025-01-06  4:59       ` Baolin Wang
2025-01-06  6:29         ` Baolin Wang

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=Z3tW-bSC6ze8HtSS@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=21cnbao@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=david@redhat.com \
    --cc=hughd@google.com \
    --cc=kasong@tencent.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ryan.roberts@arm.com \
    --cc=wangkefeng.wang@huawei.com \
    --cc=ying.huang@linux.alibaba.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