From: Usama Arif <usamaarif642@gmail.com>
To: akpm@linux-foundation.org
Cc: hannes@cmpxchg.org, shakeel.butt@linux.dev, david@redhat.com,
ying.huang@intel.com, hughd@google.com, willy@infradead.org,
yosryahmed@google.com, nphamcs@gmail.com,
chengming.zhou@linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, kernel-team@meta.com,
Usama Arif <usamaarif642@gmail.com>
Subject: [PATCH v8 0/2] mm: store zero pages to be swapped out in a bitmap
Date: Fri, 23 Aug 2024 19:57:33 +0100 [thread overview]
Message-ID: <20240823185838.939977-1-usamaarif642@gmail.com> (raw)
The original series [1] was almost merged, but was dropped
due to a last minute bug [2]. Resending this with the fix for it,
by handling zeromap in the same way as swap_map and cluster_info in
enable_swap_info, holding swapon_mutex and si->lock, hence avoiding
a race condition between swapon and any point where the lock is held.
This is the safest way.
The series had already been reviewed and acked.
Hoping that this attempt goes better than the initial one :)
This patchseries is based on top of mm-unstable from today:
4926e8348e10 - (akpm/mm-unstable) mm: optimization on page allocation when CMA enabled
[1] https://lore.kernel.org/all/20240627105730.3110705-1-usamaarif642@gmail.com/
[2] https://lore.kernel.org/all/202407101031.c6c3c651-lkp@intel.com/
Usama Arif (2):
mm: store zero pages to be swapped out in a bitmap
mm: remove code to handle same filled pages
include/linux/swap.h | 1 +
mm/page_io.c | 118 ++++++++++++++++++++++++++++++++++++++++++-
mm/swapfile.c | 38 ++++++++++++--
mm/zswap.c | 85 +++----------------------------
4 files changed, 159 insertions(+), 83 deletions(-)
--
2.43.5
next reply other threads:[~2024-08-23 18:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 18:57 Usama Arif [this message]
2024-08-23 18:57 ` [PATCH v8 1/2] mm: store zero pages to be swapped out in a bitmap Usama Arif
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=20240823185838.939977-1-usamaarif642@gmail.com \
--to=usamaarif642@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nphamcs@gmail.com \
--cc=shakeel.butt@linux.dev \
--cc=willy@infradead.org \
--cc=ying.huang@intel.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;
as well as URLs for NNTP newsgroup(s).