From: Vlastimil Babka <vbabka@suse.cz>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
kasan-dev@googlegroups.com, Qian Cai <cai@lca.pw>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Matthew Wilcox <willy@infradead.org>,
Mel Gorman <mgorman@techsingularity.net>,
Michal Hocko <mhocko@kernel.org>,
"Kirill A . Shutemov" <kirill@shutemov.name>
Subject: Re: [PATCH v2 3/3] mm, page_owner: rename flag indicating that page is allocated
Date: Mon, 30 Sep 2019 14:49:05 +0200 [thread overview]
Message-ID: <4e93dc73-191f-012b-f082-ee8730a90400@suse.cz> (raw)
In-Reply-To: <20190930122916.14969-4-vbabka@suse.cz>
On 9/30/19 2:29 PM, Vlastimil Babka wrote:
> Commit 37389167a281 ("mm, page_owner: keep owner info when freeing the page")
> has introduced a flag PAGE_EXT_OWNER_ACTIVE to indicate that page is tracked as
> being allocated. Kirril suggested naming it PAGE_EXT_OWNER_ALLOCATED to make it
^ Kirill
(again, sorry, hope Andrew can fix up if this ends up being the last
version)
prev parent reply other threads:[~2019-09-30 12:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 12:29 [PATCH v2 0/3] followups to debug_pagealloc improvements through page_owner Vlastimil Babka
2019-09-30 12:29 ` [PATCH v2 1/3] mm, page_owner: fix off-by-one error in __set_page_owner_handle() Vlastimil Babka
2019-09-30 12:29 ` [PATCH v2 2/3] mm, page_owner: decouple freeing stack trace from debug_pagealloc Vlastimil Babka
2019-09-30 12:49 ` Qian Cai
2019-09-30 21:39 ` Vlastimil Babka
2019-09-30 23:49 ` Qian Cai
2019-10-01 8:07 ` Vlastimil Babka
2019-10-01 11:51 ` Kirill A. Shutemov
2019-10-01 12:26 ` Qian Cai
2019-10-01 12:31 ` Kirill A. Shutemov
2019-10-01 12:32 ` Vlastimil Babka
2019-10-01 12:35 ` Vlastimil Babka
2019-10-01 13:18 ` Qian Cai
2019-10-01 14:15 ` Vlastimil Babka
2019-10-01 11:35 ` Kirill A. Shutemov
2019-09-30 12:29 ` [PATCH v2 3/3] mm, page_owner: rename flag indicating that page is allocated Vlastimil Babka
2019-09-30 12:49 ` Vlastimil Babka [this message]
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=4e93dc73-191f-012b-f082-ee8730a90400@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=cai@lca.pw \
--cc=kasan-dev@googlegroups.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=willy@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).