linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Yin, Fengwei" <fengwei.yin@intel.com>
To: Matthew Wilcox <willy@infradead.org>, Zi Yan <ziy@nvidia.com>
Cc: <linux-mm@kvack.org>, Andrew Morton <akpm@linux-foundation.org>,
	Yang Shi <shy828301@gmail.com>, Huang Ying <ying.huang@intel.com>,
	"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
	Ryan Roberts <ryan.roberts@arm.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] mm/migrate: put dest folio on deferred split list if source was there.
Date: Wed, 13 Mar 2024 10:33:54 +0800	[thread overview]
Message-ID: <feb2d3c1-d890-473b-8a8d-bdba11ba70c9@intel.com> (raw)
In-Reply-To: <b5017375-d43b-44f9-b931-3046ebead9cf@intel.com>



On 3/13/2024 10:07 AM, Yin, Fengwei wrote:
> 
> 
> On 3/13/2024 2:46 AM, Matthew Wilcox wrote:
>> On Tue, Mar 12, 2024 at 02:32:43PM -0400, Zi Yan wrote:
>>> On 12 Mar 2024, at 12:38, Matthew Wilcox wrote:
>>>> Folios with a positive refcount are
>>>> removed from the per-node or per-cgroup list _at which point there is
>>>> an undocumented assumption_ that they will not be removed from the
>>>> local list because they have a positive refcount.
>>>
>>> But that sounds very subtle if not broken. As an outsider of
>>
>> I merely deduced this requirement; I didn't come up with it ...
> My understanding is that this requirement is because of just local
> list in deferred_split_scan().
> 
> Using fbatch instead of local list here as your created for that
> issue debugging can eliminate this subtlety?
May not good idea because it's possible the folios in fbatch can
be removed from deferred_list by migration.

> 
> 
> Regards
> Yin, Fengwei
> 
>>
>>> deferred_split_scan(), only !list_empty(folio->_deferred_list) is 
>>> checked.
>>> The condition can be true if the folio is on split_queue or
>>> local list of deferred_split_scan() with elevated refcount. In that 
>>> case,
>>> the folio cannot be removed from the list (either split_queue or 
>>> local list)
>>> even if split_queue_lock is held, since local list manipulation is 
>>> not under
>>> split_queue_lock. This makes _deferred_list a one-way train to anyone
>>> except deferred_split_scan(), namely folios can only be added into
>>> _deferred_list until they are freed or split by deferred_split_scan().
>>>
>>> Is that intended? If yes, maybe we should document it. If not, using
>>> split_queue_lock to protect local list, or more explicitly 
>>> folio->_deferred_list
>>> might be better?
>>
>> To be fair, the folio can be split by anybody as
>> split_huge_page_to_list_to_order() is careful to only manipulate the
>> deferred list while the refcount is frozen at 0.  I'm still trying to
>> figure out where to document this behaviour of the deferred list that
>> someone (for example, your good self) would actually see it.
>>
>>
>>
> 


  reply	other threads:[~2024-03-13  2:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11 19:58 Zi Yan
2024-03-12  3:45 ` Matthew Wilcox
2024-03-12  8:05   ` Ryan Roberts
2024-03-12 14:26     ` Zi Yan
2024-03-12 14:13   ` Zi Yan
2024-03-12 14:19     ` Matthew Wilcox
2024-03-12 15:51       ` Zi Yan
2024-03-12 16:38         ` Matthew Wilcox
2024-03-12 18:32           ` Zi Yan
2024-03-12 18:46             ` Matthew Wilcox
2024-03-12 19:45               ` Zi Yan
2024-03-13  2:07               ` Yin, Fengwei
2024-03-13  2:33                 ` Yin, Fengwei [this message]
2024-03-12  7:27 ` Baolin Wang
2024-03-12 13:49   ` Zi Yan

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=feb2d3c1-d890-473b-8a8d-bdba11ba70c9@intel.com \
    --to=fengwei.yin@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ryan.roberts@arm.com \
    --cc=shy828301@gmail.com \
    --cc=willy@infradead.org \
    --cc=ying.huang@intel.com \
    --cc=ziy@nvidia.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