From: Wei Yang <richardw.yang@linux.intel.com>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Wei Yang <richardw.yang@linux.intel.com>,
hannes@cmpxchg.org, mhocko@kernel.org, vdavydov.dev@gmail.com,
ktkhai@virtuozzo.com, kirill.shutemov@linux.intel.com,
yang.shi@linux.alibaba.com, cgroups@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
alexander.duyck@gmail.com, stable@vger.kernel.org
Subject: Re: [Patch v4] mm: thp: remove the defer list related code since this will not happen
Date: Sun, 19 Jan 2020 10:24:56 +0800 [thread overview]
Message-ID: <20200119022456.GC9745@richard> (raw)
In-Reply-To: <alpine.DEB.2.21.2001181525250.27051@chino.kir.corp.google.com>
On Sat, Jan 18, 2020 at 03:36:06PM -0800, David Rientjes wrote:
>On Sat, 18 Jan 2020, Andrew Morton wrote:
>
>> On Sat, 18 Jan 2020 07:38:36 +0800 Wei Yang <richardw.yang@linux.intel.com> wrote:
>>
>> > If compound is true, this means it is a PMD mapped THP. Which implies
>> > the page is not linked to any defer list. So the first code chunk will
>> > not be executed.
>> >
>> > Also with this reason, it would not be proper to add this page to a
>> > defer list. So the second code chunk is not correct.
>> >
>> > Based on this, we should remove the defer list related code.
>> >
>> > Fixes: 87eaceb3faa5 ("mm: thp: make deferred split shrinker memcg aware")
>> >
>> > Signed-off-by: Wei Yang <richardw.yang@linux.intel.com>
>> > Suggested-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
>> > Cc: <stable@vger.kernel.org> [5.4+]
>>
>> This patch is identical to "mm: thp: grab the lock before manipulating
>> defer list", which is rather confusing. Please let people know when
>> this sort of thing is done.
>>
>> The earlier changelog mentioned a possible race condition. This
>> changelog does not. In fact this changelog fails to provide any
>> description of any userspace-visible runtime effects of the bug.
>> Please send along such a description for inclusion, as always.
>>
>
>The locking concern that Wei was originally looking at is no longer an
>issue because we determined that the code in question could simply be
>removed.
>
>I think the following can be added to the changelog:
>
>----->o-----
>
>When migrating memcg charges of thp memory, there are two possibilities:
>
> (1) The underlying compound page is mapped by a pmd and thus does is not
> on a deferred split queue (it's mapped), or
>
> (2) The compound page is not mapped by a pmd and is awaiting split on a
> deferred split queue.
>
>The current charge migration implementation does *not* migrate charges for
>thp memory on the deferred split queue, it only migrates charges for pages
>that are mapped by a pmd.
>
>Thus, to migrate charges, the underlying compound page cannot be on a
>deferred split queue; no list manipulation needs to be done in
>mem_cgroup_move_account().
>
>With the current code, the underlying compound page is moved to the
>deferred split queue of the memcg its memory is not charged to, so
>susbequent reclaim will consider these pages for the wrong memcg. Remove
>the deferred split queue handling in mem_cgroup_move_account() entirely.
>
>----->o-----
>
>Acked-by: David Rientjes <rientjes@google.com>
Hi David,
The changlog looks awesome to me. Thanks ~
Hi Andrew
I see you queue this in you tree, do I need to rewrite a patch with better
changelog?
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2020-01-19 2:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 23:38 Wei Yang
2020-01-18 0:57 ` Yang Shi
2020-01-18 5:30 ` Yang Shi
2020-01-18 22:54 ` Andrew Morton
2020-01-18 23:36 ` David Rientjes
2020-01-19 2:24 ` Wei Yang [this message]
2020-01-20 7:22 ` Michal Hocko
2020-01-20 8:17 ` Wei Yang
2020-01-20 21:10 ` David Rientjes
2020-01-20 21:27 ` Michal Hocko
2020-01-21 23:08 ` David Rientjes
2020-01-22 8:14 ` Michal Hocko
2020-01-22 23:39 ` David Rientjes
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=20200119022456.GC9745@richard \
--to=richardw.yang@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.duyck@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=ktkhai@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=rientjes@google.com \
--cc=stable@vger.kernel.org \
--cc=vdavydov.dev@gmail.com \
--cc=yang.shi@linux.alibaba.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