linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kairui Song <ryncsn@gmail.com>
To: Carsten Grohmann <carstengrohmann@gmx.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	bugzilla-daemon@kernel.org,  Baoquan He <bhe@redhat.com>,
	Nhat Pham <nphamcs@gmail.com>,
	Yosry Ahmed <yosryahmed@google.com>,
	 linux-mm@kvack.org
Subject: Re: [Bug 221055] New: Hibernate image write 10x slower since commit 0ff67f990bd4 ("mm, swap: remove swap slot cache")
Date: Fri, 13 Feb 2026 10:21:27 +0800	[thread overview]
Message-ID: <CAMgjq7C64AHL1e4HDJ22_SC7PNzU0Y3=quxDwQk0d4c04gYn3A@mail.gmail.com> (raw)
In-Reply-To: <f743bc48-b576-471a-b679-28a792822cd7@gmx.de>

Carsten Grohmann <carstengrohmann@gmx.de> 于 2026年2月13日周五 04:37写道：
>
> 12.02.2026 20:01:48 Kairui Song <ryncsn@gmail.com>:
>
> > And can anyone help verify this fix? I'll also try some other SSD later
> > maybe that's only reproducible with SSD that have very poor 4K
> > performance.
> I'll try out your patch over the weekend.

Thanks a lot!

>
> > HDD should not be affected because the allocator has a special
> > way to do HDD allocation.
> I can connect an older hard drive to my PC and test this as well. Should
> I do that? If it's not necessary, then I can save myself the effort.

That's not necessary, let's just verify the issue you reported. I have
been running swap tests on HDD for a while and hibernate uses the same
allocation method, the performance is good so far, I can double check
that.


  reply	other threads:[~2026-02-13  2:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-221055-27@https.bugzilla.kernel.org/>
2026-02-06 20:11 ` Andrew Morton
2026-02-10 18:39   ` Kairui Song
2026-02-12 19:01     ` Kairui Song
2026-02-12 20:37       ` Carsten Grohmann
2026-02-13  2:21         ` Kairui Song [this message]
2026-02-15  8:56         ` Carsten Grohmann
2026-02-15  9:25           ` Kairui Song

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='CAMgjq7C64AHL1e4HDJ22_SC7PNzU0Y3=quxDwQk0d4c04gYn3A@mail.gmail.com' \
    --to=ryncsn@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=bugzilla-daemon@kernel.org \
    --cc=carstengrohmann@gmx.de \
    --cc=linux-mm@kvack.org \
    --cc=nphamcs@gmail.com \
    --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