From: Michal Nazarewicz <mina86@mina86.com>
To: Eric Anholt <eric@anholt.net>, Michal Hocko <mhocko@kernel.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-stable <stable@vger.kernel.org>,
"Robin H. Johnson" <robbat2@orbis-terrarum.net>,
Vlastimil Babka <vbabka@suse.cz>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [PATCH] mm: Drop "PFNs busy" printk in an expected path.
Date: Sat, 31 Dec 2016 06:08:45 +0100 [thread overview]
Message-ID: <xa1t7f6g7kiq.fsf@mina86.com> (raw)
In-Reply-To: <87bmvtxizn.fsf@eliezer.anholt.net>
On Fri, Dec 30 2016, Eric Anholt wrote:
> OK, so the design is bad. When you said bug, I definitely thought you
> were saying that the message shouldn't happen in the design.
>
> Given CMA's current design, should everyone using CMA see their logs
> slowly growing with this message that is an secret code for "CMA's
> design hasn't yet changed"?
Just to be clear, it’s not CMA’s design; it’s movable page’s design that
is bad (at least in the context of this discussion).
But yes, because of the way movable pages are, everyone is likely to see
the message.
> If you want to have people be able to track how often this is
> happening, let's make a perf event for it or something instead.
Sure.
--
Best regards
ミハウ “𝓶𝓲𝓷𝓪86” ナザレヴイツ
«If at first you don’t succeed, give up skydiving»
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-12-31 5:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 2:31 Eric Anholt
2016-12-29 9:12 ` Michal Hocko
2016-12-29 17:27 ` Eric Anholt
2016-12-29 22:22 ` Michal Nazarewicz
2016-12-29 23:17 ` Eric Anholt
2016-12-30 7:11 ` Michal Nazarewicz
2016-12-30 20:25 ` Eric Anholt
2016-12-31 5:08 ` Michal Nazarewicz [this message]
2016-12-30 10:52 ` Michal Hocko
2017-01-02 7:39 ` Vlastimil Babka
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=xa1t7f6g7kiq.fsf@mina86.com \
--to=mina86@mina86.com \
--cc=eric@anholt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=mhocko@kernel.org \
--cc=robbat2@orbis-terrarum.net \
--cc=stable@vger.kernel.org \
--cc=vbabka@suse.cz \
/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