From: Hans Holmberg <hans.holmberg@wdc.com>
To: youngjun.park@lge.com
Cc: chrisl@kernel.org, linux-mm@kvack.org, hans@owltronix.com,
lsf-pc@lists.linux-foundation.org
Subject: follow up after discussion at LSF
Date: Wed, 6 May 2026 10:47:41 +0200 [thread overview]
Message-ID: <20260506084741.14228-1-hans.holmberg@wdc.com> (raw)
In-Reply-To: <aZW0voL4MmnMQlaR@yjaykim-PowerEdge-T330>
I'd just like to point out a paper by Shai Bergman:
"ZNSwap: un-Block your Swap"
https://www.usenix.org/conference/atc22/presentation/bergman
It targets ZNS SSDs but it has a lot of relevant good stuff.
next prev parent reply other threads:[~2026-05-06 8:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 12:46 [LSF/MM/BPF TOPIC] Flash Friendly Swap YoungJun Park
2026-02-20 16:22 ` Christoph Hellwig
2026-02-20 23:47 ` Chris Li
2026-02-23 13:23 ` Christoph Hellwig
2026-02-23 18:15 ` Chris Li
2026-02-23 18:53 ` Pedro Falcato
2026-02-24 2:24 ` YoungJun Park
2026-02-24 4:02 ` YoungJun Park
2026-02-24 2:15 ` YoungJun Park
2026-02-24 2:08 ` YoungJun Park
2026-05-06 8:47 ` Hans Holmberg [this message]
2026-05-06 9:12 ` follow up after discussion at LSF Chris Li
2026-05-11 1:53 ` YoungJun Park
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=20260506084741.14228-1-hans.holmberg@wdc.com \
--to=hans.holmberg@wdc.com \
--cc=chrisl@kernel.org \
--cc=hans@owltronix.com \
--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