From: Peter Xu <peterx@redhat.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Miaohe Lin <linmiaohe@huawei.com>,
Huang Ying <ying.huang@intel.com>,
David Hildenbrand <david@redhat.com>,
HORIGUCHI NAOYA <naoya.horiguchi@nec.com>,
Andrea Arcangeli <aarcange@redhat.com>,
peterx@redhat.com
Subject: [PATCH 0/2] mm: Use pte marker for swapin errors
Date: Sun, 30 Oct 2022 17:41:49 -0400 [thread overview]
Message-ID: <20221030214151.402274-1-peterx@redhat.com> (raw)
rfc->v1:
- Rename SWAP_ERROR -> SWAPIN_ERROR [David, Miaohe]
- Added r-bs for Ying and Miaohe
Hi,
This series uses the pte marker to replace the swapin error swap entry,
then we save one more swap entry slot for swap devices. A new pte marker
bit is defined.
One thing worth mentioning: we need the pte marker to be always built to
make sure it works like before, so I made an attempt in patch 1 to drop
CONFIG_PTE_MARKER and always compile pte marker in. Since pte markers are
enabled in many distributions by default already, meanwhile the codeset is
really small I assume it's fine. But still I'm tagging with RFC for this
initial version.
Smoke tested on anonymous mem on a fake swap failure. Please have a look,
thanks.
Peter Xu (2):
mm: Always compile in pte markers
mm: Use pte markers for swap errors
include/linux/swap.h | 16 ++++----------
include/linux/swapops.h | 49 +++++++++--------------------------------
mm/Kconfig | 7 ------
mm/memory.c | 13 ++++++-----
mm/shmem.c | 2 +-
mm/swapfile.c | 2 +-
6 files changed, 23 insertions(+), 66 deletions(-)
--
2.37.3
next reply other threads:[~2022-10-30 21:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 21:41 Peter Xu [this message]
2022-10-30 21:41 ` [PATCH 1/2] mm: Always compile in pte markers Peter Xu
2022-11-02 9:15 ` David Hildenbrand
2022-10-30 21:41 ` [PATCH 2/2] mm: Use pte markers for swap errors Peter Xu
2022-11-02 9:16 ` David Hildenbrand
2022-10-31 1:40 ` [PATCH 0/2] mm: Use pte marker for swapin errors Huang, Ying
2022-10-31 14:14 ` Peter Xu
2022-11-01 5:05 ` Huang, Ying
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=20221030214151.402274-1-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@nec.com \
--cc=ying.huang@intel.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