Re: [PATCH] mm: Drop "PFNs busy" printk in an expected path.

From: Michal Hocko
Date: Fri Dec 30 2016 - 05:52:11 EST

On Thu 29-12-16 23:22:20, Michal Nazarewicz wrote:
> On Thu, Dec 29 2016, Eric Anholt wrote:
> > Michal Hocko <mhocko@xxxxxxxxxx> writes:
> >
> >> This has been already brought up
> >> and there
> >> was a proposed patch for that which ratelimited the output
> >> resp.
> >>
> >>
> >> then the email thread just died out because the issue turned out to be a
> >> configuration issue. Michal indicated that the message might be useful
> >> so dropping it completely seems like a bad idea. I do agree that
> >> something has to be done about that though. Can we reconsider the
> >> ratelimit thing?
> >
> > I agree that the rate of the message has gone up during 4.9 -- it used
> > to be a few per second.
> Sounds like a regression which should be fixed.
> This is why I donât think removing the message is a good idea. If you
> suddenly see a lot of those messages, something changed for the worse.
> If you remove this message, you will never know.

I agree, that removing the message completely is not going to help to
find out regressions. Swamping logs with zillions of messages is,
however, not acceptable. It just causes even more problems. See the
previous report.

> > However, if this is an expected path during normal operation,
> This depends on your definition of âexpectedâ and ânormalâ.
> In general, I would argue that the fact those ever happen is a bug
> somewhere in the kernel â if memory is allocated as movable, it should
> be movable damn it!

Yes, it should be movable but there is no guarantee it is movable
immediately. Those pages might be pinned for some time. This is
unavoidable AFAICS.

So while this might be a regression which should be investigated there
should be another fix to prevent from swamping the logs as well.

Michal Hocko