From: Yeongjin Kwon <yeongjinkwon@gmail.com>
To: linux-mm@kvack.org
Subject: Make zswap same filled pages copy on write
Date: Thu, 16 Jun 2022 12:40:58 -0400 [thread overview]
Message-ID: <CANPvvcPzd1pf6i0iCgoF+Y=C=iJ57mcYqBOJfa=OOKrPyCJQRQ@mail.gmail.com> (raw)
Hi,
As I understand it, zswap currently handles same filled pages by
storing them uncompressed and then copying them out when they are
loaded. A possible alternative could be to have same filled pages that
get swapped out mapped to the page stored in zswap as copy on write in
the page table, instead of being marked as swapped out. Then reads
from the "swapped out" page will just read the underlying page stored
in zswap, and the stored page will only be truly loaded/copied out
when it is written to. This is similar in concept to the copy on write
mechanism the kernel has for forking processes. Would this be worth
implementing? I am largely unfamiliar with kernel development. This is
just an idea I figured I would mention here. Also please CC responses
to me, since I am not subscribed to the mailing list.
next reply other threads:[~2022-06-16 16:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 16:40 Yeongjin Kwon [this message]
2022-06-21 9:08 ` David Hildenbrand
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='CANPvvcPzd1pf6i0iCgoF+Y=C=iJ57mcYqBOJfa=OOKrPyCJQRQ@mail.gmail.com' \
--to=yeongjinkwon@gmail.com \
--cc=linux-mm@kvack.org \
/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