linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Huang, Ying" <ying.huang@intel.com>
To: Peter Xu <peterx@redhat.com>
Cc: linux-kernel@vger.kernel.org,  linux-mm@kvack.org,
	 Andrew Morton <akpm@linux-foundation.org>,
	 HORIGUCHI NAOYA <naoya.horiguchi@nec.com>,
	Miaohe Lin <linmiaohe@huawei.com>,
	 David Hildenbrand <david@redhat.com>,
	Andrea Arcangeli <aarcange@redhat.com>
Subject: Re: [PATCH RFC 0/2] mm: Use pte marker for swapin errors
Date: Tue, 25 Oct 2022 11:01:32 +0800	[thread overview]
Message-ID: <87r0ywli7n.fsf@yhuang6-desk2.ccr.corp.intel.com> (raw)
In-Reply-To: <20221024204830.1342169-1-peterx@redhat.com> (Peter Xu's message of "Mon, 24 Oct 2022 16:48:28 -0400")

Peter Xu <peterx@redhat.com> writes:

> Hi,
>
> This series uses the pte marker to replace the swapin error swap entry,
> then we safe one more swap entry.  A new pte marker bit is defined.
          ~~~~               ~~~~~
          save?              file?

It's good to save one swap file.  Thanks for your patch!  Please feel
free to add my

Reviewed-by: "Huang, Ying" <ying.huang@intel.com>

for the whole series.

Best Regards,
Huang, Ying

> 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(-)


  parent reply	other threads:[~2022-10-25  3:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24 20:48 Peter Xu
2022-10-24 20:48 ` [PATCH RFC 1/2] mm: Always compile in pte markers Peter Xu
2022-10-29  2:35   ` Miaohe Lin
2022-10-24 20:48 ` [PATCH RFC 2/2] mm: Use pte markers for swap errors Peter Xu
2022-10-25 15:31   ` David Hildenbrand
2022-10-25 15:44     ` Peter Xu
2022-10-29  2:49   ` Miaohe Lin
2022-10-25  3:01 ` Huang, Ying [this message]
2022-10-25 15:08   ` [PATCH RFC 0/2] mm: Use pte marker for swapin errors Peter Xu

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=87r0ywli7n.fsf@yhuang6-desk2.ccr.corp.intel.com \
    --to=ying.huang@intel.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=peterx@redhat.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