mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Huang, Ying" <ying.huang@intel.com>
To: David Hildenbrand <david@redhat.com>
Cc: Ryan Roberts <ryan.roberts@arm.com>,
	 Barry Song <21cnbao@gmail.com>,
	akpm@linux-foundation.org,  linux-mm@kvack.org,
	 chrisl@kernel.org, yuzhao@google.com,  hanchuanhua@oppo.com,
	 linux-kernel@vger.kernel.org, willy@infradead.org,
	 xiang@kernel.org,  mhocko@suse.com, shy828301@gmail.com,
	 wangkefeng.wang@huawei.com,  Barry Song <v-songbaohua@oppo.com>,
	 Hugh Dickins <hughd@google.com>
Subject: Re: [RFC PATCH] mm: hold PTL from the first PTE while reclaiming a large folio
Date: Tue, 05 Mar 2024 15:50:23 +0800	[thread overview]
Message-ID: <87v86186dc.fsf@yhuang6-desk2.ccr.corp.intel.com> (raw)
In-Reply-To: <37f1e6da-412b-4bb4-88b7-4c49f21f5fe9@redhat.com> (David Hildenbrand's message of "Mon, 4 Mar 2024 13:41:38 +0100")

David Hildenbrand <david@redhat.com> writes:
>
> As we are seeing more such problems with lockless PT walks, maybe we
> really want some other special value (nonswap entry?) to indicate that
> a PTE this is currently ondergoing protection changes. So we'd avoid
> the pte_none() temporarily, if possible.

This sounds like a good idea.  This can solve other issue caused by
temporarily pte_none() issue too, like the following,

https://lore.kernel.org/linux-mm/20240229060907.836589-1-zhangpeng362@huawei.com/

--
Best Regards,
Huang, Ying

  parent reply	other threads:[~2024-03-05  7:52 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04 10:37 Barry Song
2024-03-04 12:20 ` Ryan Roberts
2024-03-04 12:41   ` David Hildenbrand
2024-03-04 13:03     ` Ryan Roberts
2024-03-04 14:27       ` David Hildenbrand
2024-03-04 20:42         ` Barry Song
2024-03-04 21:02           ` David Hildenbrand
2024-03-04 21:41             ` Barry Song
2024-03-04 21:04     ` Barry Song
2024-03-04 21:15       ` David Hildenbrand
2024-03-04 22:29         ` Barry Song
2024-03-05  7:53           ` Huang, Ying
2024-03-05  9:02             ` Barry Song
2024-03-05  9:10               ` Huang, Ying
2024-03-05  9:21                 ` Barry Song
2024-03-05 10:28                   ` Barry Song
2024-03-04 22:02       ` Ryan Roberts
2024-03-05  7:50     ` Huang, Ying [this message]
2024-03-04 21:57   ` Barry Song
2024-03-05  8:54     ` Ryan Roberts
2024-03-05  9:08       ` Barry Song
2024-03-05  9:11         ` Ryan Roberts
2024-03-05  9:15           ` Barry Song
2024-03-05  7:28 ` Huang, Ying
2024-03-05  8:56   ` Barry Song
2024-03-05  9:04     ` Huang, Ying
2024-03-05  9:08     ` Ryan Roberts
2024-03-05  9:11       ` Barry Song

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=87v86186dc.fsf@yhuang6-desk2.ccr.corp.intel.com \
    --to=ying.huang@intel.com \
    --cc=21cnbao@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=chrisl@kernel.org \
    --cc=david@redhat.com \
    --cc=hanchuanhua@oppo.com \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=ryan.roberts@arm.com \
    --cc=shy828301@gmail.com \
    --cc=v-songbaohua@oppo.com \
    --cc=wangkefeng.wang@huawei.com \
    --cc=willy@infradead.org \
    --cc=xiang@kernel.org \
    --cc=yuzhao@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

all inboxes | Powered by JetHome®