From: Eric Anholt <eric@anholt.net>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org, Eric Anholt <eric@anholt.net>,
linux-stable <stable@vger.kernel.org>
Subject: [PATCH] mm: Drop "PFNs busy" printk in an expected path.
Date: Wed, 28 Dec 2016 18:31:31 -0800 [thread overview]
Message-ID: <20161229023131.506-1-eric@anholt.net> (raw)
For CMA allocations, we expect to occasionally hit this error path, at
which point CMA will retry. Given that, we shouldn't be spamming
dmesg about it.
The Raspberry Pi graphics driver does frequent CMA allocations, and
during regression testing this printk was sometimes occurring 100s of
times per second.
Signed-off-by: Eric Anholt <eric@anholt.net>
Cc: linux-stable <stable@vger.kernel.org>
---
mm/page_alloc.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index 6de9440e3ae2..bea7204c14a5 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -7289,8 +7289,6 @@ int alloc_contig_range(unsigned long start, unsigned long end,
/* Make sure the range is really isolated. */
if (test_pages_isolated(outer_start, end, false)) {
- pr_info("%s: [%lx, %lx) PFNs busy\n",
- __func__, outer_start, end);
ret = -EBUSY;
goto done;
}
--
2.11.0
--
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 reply other threads:[~2016-12-29 2:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 2:31 Eric Anholt [this message]
2016-12-29 9:12 ` [PATCH] mm: Drop "PFNs busy" printk in an expected path 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
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=20161229023131.506-1-eric@anholt.net \
--to=eric@anholt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=stable@vger.kernel.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).