From: Christoph Hellwig <hch@infradead.org>
To: YoungJun Park <youngjun.park@lge.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org, chrisl@kernel.org
Subject: Re: [LSF/MM/BPF TOPIC] Flash Friendly Swap
Date: Fri, 20 Feb 2026 08:22:27 -0800 [thread overview]
Message-ID: <aZiKQwT7KjWDLspH@infradead.org> (raw)
In-Reply-To: <aZW0voL4MmnMQlaR@yjaykim-PowerEdge-T330>
Honestly, I think always writing sequentially when swapping and
reclaiming in lumps (I'd call them "zones" :)) is probably the best
idea. Even for the these days unlikely case of swapping to HDD it
would do the right thing. So please no conditional version that need
opt-in or stacked block drivers, let's just fix swapping to not be
stupid.
next prev parent reply other threads:[~2026-02-20 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 12:46 YoungJun Park
2026-02-20 16:22 ` Christoph Hellwig [this message]
2026-02-20 23:47 ` Chris Li
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=aZiKQwT7KjWDLspH@infradead.org \
--to=hch@infradead.org \
--cc=chrisl@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=youngjun.park@lge.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