Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753800AbcL3KwI (ORCPT ); Fri, 30 Dec 2016 05:52:08 -0500 Received: from mx2.suse.de ([195.135.220.15]:47254 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753649AbcL3KwH (ORCPT ); Fri, 30 Dec 2016 05:52:07 -0500 Date: Fri, 30 Dec 2016 11:52:00 +0100 From: Michal Hocko To: Michal Nazarewicz Cc: Eric Anholt , linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-stable , "Robin H. Johnson" , Vlastimil Babka , Marek Szyprowski Subject: Re: [PATCH] mm: Drop "PFNs busy" printk in an expected path. Message-ID: <20161230105200.GE13301@dhcp22.suse.cz> References: <20161229023131.506-1-eric@anholt.net> <20161229091256.GF29208@dhcp22.suse.cz> <87wpeitzld.fsf@eliezer.anholt.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2011 Lines: 48 On Thu 29-12-16 23:22:20, Michal Nazarewicz wrote: > On Thu, Dec 29 2016, Eric Anholt wrote: > > Michal Hocko writes: > > > >> This has been already brought up > >> http://lkml.kernel.org/r/20161130092239.GD18437@dhcp22.suse.cz and there > >> was a proposed patch for that which ratelimited the output > >> http://lkml.kernel.org/r/20161130132848.GG18432@dhcp22.suse.cz resp. > >> http://lkml.kernel.org/r/robbat2-20161130T195244-998539995Z@orbis-terrarum.net > >> > >> 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 SUSE Labs