Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753180AbcL2WWd (ORCPT ); Thu, 29 Dec 2016 17:22:33 -0500 Received: from mail-lf0-f48.google.com ([209.85.215.48]:34313 "EHLO mail-lf0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752993AbcL2WWa (ORCPT ); Thu, 29 Dec 2016 17:22:30 -0500 From: Michal Nazarewicz To: Eric Anholt , Michal Hocko Cc: 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. In-Reply-To: <87wpeitzld.fsf@eliezer.anholt.net> Organization: http://mina86.com/ References: <20161229023131.506-1-eric@anholt.net> <20161229091256.GF29208@dhcp22.suse.cz> <87wpeitzld.fsf@eliezer.anholt.net> User-Agent: Notmuch/0.19+53~g2e63a09 (http://notmuchmail.org) Emacs/26.0.50.2 (x86_64-unknown-linux-gnu) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEWbfGlUPDDHgE57V0jUupKjgIObY0PLrom9mH4dFRK4gmjPs41MxjOgAAACP0lEQVQ4T23Sv2vbQBQHcBk1xE6WyALX107VUEgmn6+ouUwpEQQ6uRjttkWP4CkBg2M0BQLBdPFZYPsyFYo7qEtKDQ7on+t7+nF2Ux8ahD587717OmNYrOvycHsZ+o2r051wHTHysAvGb8ygvgu4QWT0sCmkgZCIEnlV2X8BtyraazFGDuxhmKSQJMlwHQ7v5MHSNxmz78rfElwAa3ieVD9e+hBhjaPDDG6NgFo2f4wBMNIo5YmRtF0RyDgFjJjlMIWbnuM4x9MMfABGTlN4qgIQB4A1DEyA1BHWtfeWNUMwiVJKoqh97KrkOO+qzgluVYLvFCUKAX73nONeBr7BGMdM6Sg0kuep03VywLaIzRiVr+GAzKlpQIsAFnWAG2e6DT5WmWDiudZMIc6hYrMOmeMQK9WX0B+/RfjzL9DI7Y9/Iayn29Ci0r2i4f9gMimMSZLCDMalgQGU5hnUtqAN0OGvEmO1Wnl0C0wWSCEHnuHBqmygxdxA8oWXwbipoc1EoNR9DqOpBpOJrnr0criQab9ZT4LL+wI+K7GBQH30CrhUruilgP9DRTrhVWZCiAyILP+wiuLeCKGTD6r/nc8LOJcAwR6IBTUs+7CASw3QFZ0MdA2PI3zNziH4ZKVhXCRMBjeZ1DWMekKwDCASwExy+NQ86TaykaDAFHO4aP48y4fIcDM5yOG8GcTLbOyp8A8azjJI93JFd1EA6yN8sSxMQJWoABqniRZVykYgRXErzrdqExAoUrRb0xfRp8p2A/4XmfilTtkDZ4cAAAAASUVORK5CYII= X-Face: -TR8(rDTHy/(xl?SfWd1|3:TTgDIatE^t'vop%*gVg[kn$t{EpK(P"VQ=~T2#ysNmJKN$"yTRLB4YQs$4{[.]Fc1)*O]3+XO^oXM>Q#b^ix,O)Zbn)q[y06$`e3?C)`CwR9y5riE=fv^X@x$y?D:XO6L&x4f-}}I4=VRNwiA^t1-ZrVK^07.Pi/57c_du'& X-PGP: 50751FF4 X-PGP-FP: AC1F 5F5C D418 88F8 CC84 5858 2060 4012 5075 1FF4 X-Hashcash: 1:20:161229:vbabka@suse.cz::/9gP8d/Rpe5HzsYt:00005MW X-Hashcash: 1:20:161229:eric@anholt.net::ZtfTanWgDz60u7ig:002tZj X-Hashcash: 1:20:161229:m.szyprowski@samsung.com::VxOBOPTbEetAAK1Y:00000000000000000000000000000000000002xQV X-Hashcash: 1:20:161229:mhocko@kernel.org::V1tpqkfPI+dGHXDv:000000000000000000000000000000000000000000004Pxr X-Hashcash: 1:20:161229:linux-kernel@vger.kernel.org::2TDGpfNR3m/ZciBS:0000000000000000000000000000000004Dmz X-Hashcash: 1:20:161229:robbat2@orbis-terrarum.net::RvVl7JZ4BAtmk6Es:000000000000000000000000000000000007nzd X-Hashcash: 1:20:161229:stable@vger.kernel.org::OMdpZFTzoB8RJRWv:000000000000000000000000000000000000000CZ6Q X-Hashcash: 1:20:161229:linux-mm@kvack.org::vjQWrNeP6vXGlGjh:0000000000000000000000000000000000000000000LeKf Date: Thu, 29 Dec 2016 23:22:20 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.home.local id uBTMMblY031216 Content-Length: 1801 Lines: 42 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. > 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! > we shouldn't be clogging dmesg with it at all. So, I'd rather we go > with this patch, that is unless the KERN_DEBUG in your ratelimit patch > would keep it out of journald as well (un-ratelimited, journald was > eating 10% of a CPU processing the message, and I'd rather it not be > getting logged at all). -- Best regards ミハウ “????????????????86” ナザレヴイツ «If at first you don’t succeed, give up skydiving»